# CVE-2005-2471: Command injection in n/a

> Attackers can execute arbitrary commands via malicious PostScript files due to improper Ghostscript sandboxing in pstopnm.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2471, DSA-1021-1, GHSA-9hfq-3c4w-mxr2, RHSA-2005:743

## What is CVE-2005-2471?

CVE-2005-2471 is a high-severity command injection vulnerability in n/a, published on 5 Aug 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

pstopnm in netpbm does not properly use the "-dSAFER" option when calling Ghostscript to convert a PostScript file into a (1) PBM, (2) PGM, or (3) PNM file, which allows external user-assisted attackers to execute arbitrary commands.

## Which versions are affected by CVE-2005-2471?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netpbm` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.2 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.2 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.2 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::as | All versions | 0:9.24-11.30.2 |
| `netpbm` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.2 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.2 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.2 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:9.24-11.30.2 |
| `netpbm` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.2 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.2 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.2 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::es | All versions | 0:9.24-11.30.2 |
| `netpbm` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.2 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.2 |
| `netpbm-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.2 |
| `netpbm-progs` | Red Hat:enterprise_linux:3::ws | All versions | 0:9.24-11.30.2 |
| `netpbm` | Red Hat:enterprise_linux:4::as | All versions | 0:10.25-2.EL4.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:10.25-2.EL4.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:10.25-2.EL4.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:4::as | All versions | 0:10.25-2.EL4.1 |
| `netpbm` | Red Hat:enterprise_linux:4::desktop | All versions | 0:10.25-2.EL4.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:10.25-2.EL4.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:10.25-2.EL4.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:10.25-2.EL4.1 |
| `netpbm` | Red Hat:enterprise_linux:4::es | All versions | 0:10.25-2.EL4.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:10.25-2.EL4.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:10.25-2.EL4.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:4::es | All versions | 0:10.25-2.EL4.1 |
| `netpbm` | Red Hat:enterprise_linux:4::ws | All versions | 0:10.25-2.EL4.1 |
| `netpbm-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:10.25-2.EL4.1 |
| `netpbm-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:10.25-2.EL4.1 |
| `netpbm-progs` | Red Hat:enterprise_linux:4::ws | All versions | 0:10.25-2.EL4.1 |

Products: Netpbm Netpbm.

## How do I fix CVE-2005-2471?

Apply the vendor's patch.

## Is CVE-2005-2471 being exploited?

There is no known exploitation of CVE-2005-2471 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-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)
- [CVE-2006-3145](https://insights.sbomify.com/CVE-2006-3145/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2471 and fix it if it is affected.

What it is: CVE-2005-2471 is a high-severity command injection vulnerability in n/a, published on 5 Aug 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-2471 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-2005-2471/ (Markdown: https://insights.sbomify.com/CVE-2005-2471/index.md)
```

## Sources

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

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