# CVE-2009-4134: Memory corruption in n/a

> Remote attackers can crash Python applications by sending a malformed black-and-white RGB image with a large ZSIZE value.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5g97-f544-j8g3, PSF-2010-1

## What is CVE-2009-4134?

CVE-2009-4134 is a medium-severity memory corruption vulnerability in Python Python, published on 27 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer underflow in the rgbimg module in Python 2.5 allows remote attackers to cause a denial of service (application crash) via a large ZSIZE value in a black-and-white (aka B/W) RGB image that triggers an invalid pointer dereference.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2009-4134?

It affects 1 product.


Products: Python Python.

## How do I fix CVE-2009-4134?

Upgrade to a fixed version.

## Is CVE-2009-4134 being exploited?

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

## Other vulnerabilities in Python Python

- [CVE-2008-5031](https://insights.sbomify.com/CVE-2008-5031/): Integer overflow in n/a (critical 10.0)
- [CVE-2014-4650](https://insights.sbomify.com/CVE-2014-4650/): Path traversal in n/a (critical 9.8)
- [CVE-2016-5636](https://insights.sbomify.com/CVE-2016-5636/): Integer overflow in n/a (critical 9.8)
- [CVE-2007-4559](https://insights.sbomify.com/CVE-2007-4559/): Path traversal in n/a (critical 9.8)
- [CVE-2017-17522](https://insights.sbomify.com/CVE-2017-17522/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4134 and fix it if it is affected.

What it is: CVE-2009-4134 is a medium-severity memory corruption vulnerability in Python Python, published on 27 May 2010. 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-2009-4134 in the wild and no public exploit code.

Affected product: Python Python. 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-2009-4134/ (Markdown: https://insights.sbomify.com/CVE-2009-4134/index.md)
```

## Sources

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

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