# CVE-2005-1141: Integer overflow in n/a

> Remote attackers can execute arbitrary code via a crafted PNM file due to an integer overflow leading to heap corruption in GOCR.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1141, GHSA-ghqg-gfm6-qhh6

## What is CVE-2005-1141?

CVE-2005-1141 is a critical vulnerability in n/a, published on 16 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the readpgm function in pnm.c for GOCR 0.40, when using the netpbm library, allows remote attackers to execute arbitrary code via a PNM file with large width and height values, which leads to a heap-based buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Optical Character Recognition Project Optical Character Recognition.

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

Upgrade to a fixed version.

## Is CVE-2005-1141 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33479](https://insights.sbomify.com/CVE-2021-33479/): Memory corruption in gocr (high 7.8)
- [CVE-2021-33481](https://insights.sbomify.com/CVE-2021-33481/): Memory corruption in gocr (high 7.8)
- [CVE-2021-33480](https://insights.sbomify.com/CVE-2021-33480/): Use after free in gocr (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1141 is a critical vulnerability in n/a, published on 16 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1141 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-1141/ (Markdown: https://insights.sbomify.com/CVE-2005-1141/index.md)
```

## Sources

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

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