# CVE-2023-42017: IBM Planning Analytics file upload

> Remote attackers can upload malicious scripts to IBM Planning Analytics Local, leading to arbitrary code execution on the server.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 22 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-43rj-vhj3-86r7

## What is CVE-2023-42017?

CVE-2023-42017 is a high-severity vulnerability in IBM Planning Analytics, published on 22 Dec 2023. 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 Planning Analytics Local 2.0 could allow a remote attacker to upload arbitrary files, caused by the improper validation of file extensions.  By sending a specially crafted HTTP request, a remote attacker could exploit this vulnerability to upload a malicious script, which could allow the attacker to execute arbitrary code on the vulnerable system.  IBM X-Force ID:  265567.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-42017?

It affects 1 product.


Products: Ibm Planning Analytics.

## How do I fix CVE-2023-42017?

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

## Is CVE-2023-42017 being exploited?

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

## Other vulnerabilities in IBM Planning Analytics

- [CVE-2019-4716](https://insights.sbomify.com/CVE-2019-4716/): IBM Planning Analytics Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2026-19620](https://insights.sbomify.com/CVE-2026-19620/): IBM Planning Analytics Local is affected by security vulnerabilities (high 8.8)
- [CVE-2026-19622](https://insights.sbomify.com/CVE-2026-19622/): IBM Planning Analytics Local is affected by security vulnerabilities (high 8.8)
- [CVE-2026-19627](https://insights.sbomify.com/CVE-2026-19627/): IBM Planning Analytics Local is affected by security vulnerabilities (high 8.2)
- [CVE-2024-25034](https://insights.sbomify.com/CVE-2024-25034/): IBM Planning Analytics file upload (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42017 and fix it if it is affected.

What it is: CVE-2023-42017 is a high-severity vulnerability in IBM Planning Analytics, published on 22 Dec 2023. 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-2023-42017 in the wild and no public exploit code.

Affected product: IBM Planning Analytics. 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-2023-42017/ (Markdown: https://insights.sbomify.com/CVE-2023-42017/index.md)
```

## Sources

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

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