# CVE-2023-38003: IBM Db2 command execution

> A user with DATAACCESS privileges can execute unauthorized routines, leading to privilege escalation and potential code execution in IBM Db2.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2023
- **Updated:** 29 May 2025
- **Also known as:** GHSA-h4pg-gh86-xfpg

## What is CVE-2023-38003?

CVE-2023-38003 is a high-severity vulnerability in Ibm Db2, published on 4 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 10.5, 11.1, and 11.5 could allow a user with DATAACCESS privileges to execute routines that they should not have access to.  IBM X-Force ID:  260214.

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

It affects 1 product.


Products: Ibm Db2.

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

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

## Is CVE-2023-38003 being exploited?

There is no known exploitation of CVE-2023-38003 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-38003 and fix it if it is affected.

What it is: CVE-2023-38003 is a high-severity vulnerability in Ibm Db2, published on 4 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38003 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-38003/ (Markdown: https://insights.sbomify.com/CVE-2023-38003/index.md)
```

## Sources

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

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