# CVE-2003-0289: Memory corruption in n/a

> Local attackers can exploit a format string vulnerability in cdrtools to execute arbitrary code and gain elevated privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xp7j-9g27-rqpj

## What is CVE-2003-0289?

CVE-2003-0289 is a high-severity memory corruption vulnerability in n/a, published on 14 May 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Format string vulnerability in scsiopen.c of the cdrecord program in cdrtools 2.0 allows local users to gain privileges via format string specifiers in the dev parameter.

## Which versions are affected by CVE-2003-0289?

It affects 1 product.


Products: Cdrtools Cdrecord.

## How do I fix CVE-2003-0289?

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

## Is CVE-2003-0289 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0289 exists.

Public exploit code:

- CDRTools CDRecord 1.11/2.0 - Devname Format String (exploitdb)
- CDRTools CDRecord 2.0 (Mandrake / Slackware) - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0806](https://insights.sbomify.com/CVE-2004-0806/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-0866](https://insights.sbomify.com/CVE-2005-0866/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0289 and fix it if it is affected.

What it is: CVE-2003-0289 is a high-severity memory corruption vulnerability in n/a, published on 14 May 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0289 exists.

Affected product: n/a. 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-2003-0289/ (Markdown: https://insights.sbomify.com/CVE-2003-0289/index.md)
```

## Sources

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

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