# CVE-2005-3193: 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 files.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 7 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3193, GHSA-92gm-9hj8-rfmw

## What is CVE-2005-3193?

CVE-2005-3193 is a medium-severity memory corruption vulnerability in n/a, published on 7 Dec 2005. 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 the JPXStream::readCodestream function in the JPX stream parsing code (JPXStream.c) for xpdf 3.01 and earlier, as used in products such as (1) Poppler, (2) teTeX, (3) KDE kpdf, (4) CUPS, and (5) libextractor allows user-assisted attackers to cause a denial of service (heap corruption) and possibly execute arbitrary code via a crafted PDF file with large size values that cause insufficient memory to be allocated.

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

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

It affects 1 product.


Products: Xpdf Xpdf.

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

Upgrade to a fixed version.

## Is CVE-2005-3193 being exploited?

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

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

## Sources

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

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