# CVE-2021-39017: File upload in Engineering Lifecycle Optimization Publishing

> Remote attackers can upload arbitrary files due to improper access controls, potentially leading to code execution.

- **Severity:** Medium 5.7 (`CVSS:3.0/I:H/C:N/PR:L/UI:R/A:N/AV:N/S:U/AC:L/RL:O/E:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c9c3-p4fc-fg34

## What is CVE-2021-39017?

CVE-2021-39017 is a medium-severity vulnerability in IBM Engineering Lifecycle Optimization Publishing, published on 14 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

IBM Engineering Lifecycle Optimization - Publishing 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2 could allow a remote attacker to upload arbitrary files, caused by improper access controls. IBM X-Force ID: 213725.

## Which versions are affected by CVE-2021-39017?

It affects 2 products.


Products: Ibm Engineering Lifecycle Optimization - Publishing, Ibm Engineering Lifecycle Optimization Publishing.

## How do I fix CVE-2021-39017?

No fix has been published for CVE-2021-39017 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-39017 being exploited?

There is no known exploitation of CVE-2021-39017 in the wild and no public exploit code.

## Other vulnerabilities in IBM Engineering Lifecycle Optimization Publishing

- [CVE-2021-39019](https://insights.sbomify.com/CVE-2021-39019/): Information disclosure in Engineering Lifecycle Optimization Publishing (medium 6.5)
- [CVE-2021-39015](https://insights.sbomify.com/CVE-2021-39015/): Cross-site scripting in Engineering Lifecycle Optimization Publishing (medium 5.4)
- [CVE-2021-39028](https://insights.sbomify.com/CVE-2021-39028/): Cross-site scripting in Engineering Lifecycle Optimization Publishing (medium 5.4)
- [CVE-2019-4431](https://insights.sbomify.com/CVE-2019-4431/): Cross-site scripting in Rational Publishing Engine (medium 5.4)
- [CVE-2018-1657](https://insights.sbomify.com/CVE-2018-1657/): Cross-site scripting in Rational Publishing Engine (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39017 and fix it if it is affected.

What it is: CVE-2021-39017 is a medium-severity vulnerability in IBM Engineering Lifecycle Optimization Publishing, published on 14 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-39017 in the wild and no public exploit code.

Affected product: IBM Engineering Lifecycle Optimization Publishing. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-39017/ (Markdown: https://insights.sbomify.com/CVE-2021-39017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-39017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-39017
- OSV: https://osv.dev/vulnerability/CVE-2021-39017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-39017/
Summaries are generated and may contain mistakes; the official description above is the record.