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

> Attackers can execute arbitrary code via malicious PDF files due to unchecked values in Xpdf's DCTDecode stream processing.

- **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:** 6 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3627, GHSA-738f-c7mc-xp78

## What is CVE-2005-3627?

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

Stream.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 a DCTDecode stream with (1) a large "number of components" value that is not checked by DCTStream::readBaselineSOF or DCTStream::readProgressiveSOF, (2) a large "Huffman table index" value that is not checked by DCTStream::readHuffmanTables, and (3) certain uses of the scanInfo.numComps value by DCTStream::readScanInfo.

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

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

It affects 1 product.


Products: Xpdf Xpdf.

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

Upgrade to a fixed version.

## Is CVE-2005-3627 being exploited?

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

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

## Sources

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

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