# CVE-2007-2052: Memory corruption in n/a

> An off-by-one error in Python's locale module allows attackers to read sensitive memory via buffer over-reads.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7hcx-rxp8-j55g

## What is CVE-2007-2052?

CVE-2007-2052 is a medium-severity memory corruption vulnerability in Python Python, published on 16 Apr 2007. 

### Official description

Off-by-one error in the PyLocale_strxfrm function in Modules/_localemodule.c for Python 2.4 and 2.5 causes an incorrect buffer size to be used for the strxfrm function, which allows context-dependent attackers to read portions of memory via unknown manipulations that trigger a buffer over-read due to missing null termination.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2007-2052?

It affects 1 product.


Products: Python Python.

## How do I fix CVE-2007-2052?

Upgrade to a fixed version.

## Is CVE-2007-2052 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2052 exists.

Public exploit code:

- Python 2.5 - 'PyLocale_strxfrm' Remote Information Leak (exploitdb)

## 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-2007-2052 and fix it if it is affected.

What it is: CVE-2007-2052 is a medium-severity memory corruption vulnerability in Python Python, published on 16 Apr 2007. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2052 exists.

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-2007-2052/ (Markdown: https://insights.sbomify.com/CVE-2007-2052/index.md)
```

## Sources

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

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