# CVE-2005-3628: Memory corruption in n/a

> A buffer overflow in Xpdf's JBIG2 bitmap handling allows attackers to execute arbitrary code via malicious PDF files.

- **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:** 23 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3628, GHSA-c67q-9hxp-64hm

## What is CVE-2005-3628?

CVE-2005-3628 is a high-severity memory corruption vulnerability in n/a, published on 23 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

Buffer overflow in the JBIG2Bitmap::JBIG2Bitmap function in JBIG2Stream.cc in Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to modify memory and possibly execute arbitrary code via unknown attack vectors.

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

It affects 1 product.


Products: Xpdf Xpdf.

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

Upgrade to a fixed version.

## Is CVE-2005-3628 being exploited?

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

What it is: CVE-2005-3628 is a high-severity memory corruption vulnerability in n/a, published on 23 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-2005-3628 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-3628/ (Markdown: https://insights.sbomify.com/CVE-2005-3628/index.md)
```

## Sources

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

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