# CVE-2003-0924: Path traversal in n/a

> Local attackers can overwrite arbitrary files due to insecure temporary file creation in the Netpbm image processing library.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0924, DSA-426, GHSA-4rcx-3v3w-9cg9, RHSA-2004:031

## What is CVE-2003-0924?

CVE-2003-0924 is a low-severity path traversal vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

netpbm 9.25 and earlier does not properly create temporary files, which allows local users to overwrite arbitrary files.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netpbm` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.1 |
| `netpbm` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.1 |
| `netpbm` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.1 |
| `netpbm` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.1 |

Products: Netpbm Netpbm.

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

Upgrade to a fixed version.

## Is CVE-2003-0924 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4274](https://insights.sbomify.com/CVE-2009-4274/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2978](https://insights.sbomify.com/CVE-2005-2978/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2471](https://insights.sbomify.com/CVE-2005-2471/): Command injection in n/a (high 7.5)
- [CVE-2003-0146](https://insights.sbomify.com/CVE-2003-0146/): Integer overflow in n/a (high 7.5)
- [CVE-2008-0554](https://insights.sbomify.com/CVE-2008-0554/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0924 is a low-severity path traversal vulnerability in n/a, published on 1 Sep 2004. 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-2003-0924 in the wild and no public exploit code.

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-0924/ (Markdown: https://insights.sbomify.com/CVE-2003-0924/index.md)
```

## Sources

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

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