# CVE-2023-42005: IBM Db2 on Cloud Pak for Data privilege escalation

> A user with Kubernetes pod access can make system calls to compromise container security in IBM Db2 on Cloud Pak for Data.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2024
- **Updated:** 2 Aug 2024

## What is CVE-2023-42005?

CVE-2023-42005 is a high-severity vulnerability in Ibm Db2, published on 29 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data 3.5, 4.0, 4.5, 4.6, 4.7, and 4.8 could allow a user with access to the Kubernetes pod, to make system calls compromising the security of containers. IBM X-Force ID: 265264.

Weakness: CWE-264

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

It affects 2 products.


Products: Ibm Db2, Ibm Db2 Warehouse.

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

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

## Is CVE-2023-42005 being exploited?

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

## Other vulnerabilities in Ibm Db2

- [CVE-2012-1797](https://insights.sbomify.com/CVE-2012-1797/): IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors. (critical 10.0)
- [CVE-2010-3731](https://insights.sbomify.com/CVE-2010-3731/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-3193](https://insights.sbomify.com/CVE-2010-3193/): Other in n/a (critical 10.0)
- [CVE-2009-4335](https://insights.sbomify.com/CVE-2009-4335/): Other in n/a (critical 10.0)
- [CVE-2009-3473](https://insights.sbomify.com/CVE-2009-3473/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42005 is a high-severity vulnerability in Ibm Db2, published on 29 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-42005 in the wild and no public exploit code.

Affected product: Ibm Db2. 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-42005/ (Markdown: https://insights.sbomify.com/CVE-2023-42005/index.md)
```

## Sources

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

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