# CVE-2024-52899: IBM Data Virtualization Manager code execution

> Authenticated users can inject malicious JDBC URL parameters to execute arbitrary code on the server.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-3qrf-2xj8-m9mv

## What is CVE-2024-52899?

CVE-2024-52899 is a high-severity code injection vulnerability in IBM Data Virtualization Manager for z/OS, published on 26 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Data Virtualization Manager for z/OS 1.1 and 1.2 could allow an authenticated user to inject malicious JDBC URL parameters and execute code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-52899?

It affects 1 product.


Products: Ibm Data Virtualization Manager for Z\/Os.

## How do I fix CVE-2024-52899?

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

## Is CVE-2024-52899 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52899 and fix it if it is affected.

What it is: CVE-2024-52899 is a high-severity code injection vulnerability in IBM Data Virtualization Manager for z/OS, published on 26 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52899 in the wild and no public exploit code.

Affected product: IBM Data Virtualization Manager for z/OS. 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-2024-52899/ (Markdown: https://insights.sbomify.com/CVE-2024-52899/index.md)
```

## Sources

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

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