# CVE-2006-0301: Memory corruption in n/a

> Heap-based buffer overflow in xpdf allows attackers to execute arbitrary code or cause denial of service via crafted PDF images.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0301, DSA-971-1, DSA-972-1, DSA-974-1, DSA-998-1, GHSA-rj3h-g34f-3227, RHSA-2006:0201, RHSA-2006:0206

## What is CVE-2006-0301?

CVE-2006-0301 is a high-severity memory corruption vulnerability in n/a, published on 30 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in Splash.cc in xpdf, as used in other products such as (1) poppler, (2) kdegraphics, (3) gpdf, (4) pdfkit.framework, and others, allows attackers to cause a denial of service and possibly execute arbitrary code via crafted splash images that produce certain values that exceed the width or height of the associated bitmap.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2006-0301?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdegraphics` | Red Hat:enterprise_linux:4::as | All versions | 7:3.3.1-3.7 |
| `kdegraphics-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 7:3.3.1-3.7 |
| `kdegraphics-devel` | Red Hat:enterprise_linux:4::as | All versions | 7:3.3.1-3.7 |
| `xpdf` | Red Hat:enterprise_linux:4::as | All versions | 1:3.00-11.12 |
| `xpdf-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:3.00-11.12 |
| `kdegraphics` | Red Hat:enterprise_linux:4::desktop | All versions | 7:3.3.1-3.7 |
| `kdegraphics-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 7:3.3.1-3.7 |
| `kdegraphics-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 7:3.3.1-3.7 |
| `xpdf` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.00-11.12 |
| `xpdf-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.00-11.12 |
| `kdegraphics` | Red Hat:enterprise_linux:4::es | All versions | 7:3.3.1-3.7 |
| `kdegraphics-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 7:3.3.1-3.7 |
| `kdegraphics-devel` | Red Hat:enterprise_linux:4::es | All versions | 7:3.3.1-3.7 |
| `xpdf` | Red Hat:enterprise_linux:4::es | All versions | 1:3.00-11.12 |
| `xpdf-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:3.00-11.12 |
| `kdegraphics` | Red Hat:enterprise_linux:4::ws | All versions | 7:3.3.1-3.7 |
| `kdegraphics-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 7:3.3.1-3.7 |
| `kdegraphics-devel` | Red Hat:enterprise_linux:4::ws | All versions | 7:3.3.1-3.7 |
| `xpdf` | Red Hat:enterprise_linux:4::ws | All versions | 1:3.00-11.12 |
| `xpdf-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:3.00-11.12 |

Products: Xpdf Xpdf.

## How do I fix CVE-2006-0301?

Apply the vendor's patch.

## Is CVE-2006-0301 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5392](https://insights.sbomify.com/CVE-2007-5392/): Integer overflow in n/a (critical 9.3)
- [CVE-2007-5393](https://insights.sbomify.com/CVE-2007-5393/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4352](https://insights.sbomify.com/CVE-2007-4352/): Memory corruption in n/a (high 7.6)
- [CVE-2000-0727](https://insights.sbomify.com/CVE-2000-0727/): Command injection in n/a (high 7.6)
- [CVE-2006-0746](https://insights.sbomify.com/CVE-2006-0746/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0301 and fix it if it is affected.

What it is: CVE-2006-0301 is a high-severity memory corruption vulnerability in n/a, published on 30 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0301 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-2006-0301/ (Markdown: https://insights.sbomify.com/CVE-2006-0301/index.md)
```

## Sources

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

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