# CVE-2006-1542: Memory corruption in n/a

> Local attackers can trigger a stack-based buffer overflow in Python via long directory names, potentially executing code or escalating privileges.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** AZL-109548, GHSA-75w6-c37p-69v3

## What is CVE-2006-1542?

CVE-2006-1542 is a low-severity memory corruption vulnerability in Python Python, published on 30 Mar 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function.  NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.

## Which versions are affected by CVE-2006-1542?

It affects 1 product.


Products: Python Python.

## How do I fix CVE-2006-1542?

Upgrade to a fixed version.

## Is CVE-2006-1542 being exploited?

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

Public exploit code:

- Python 2.4.2 - 'realpath()' Local Stack Overflow (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-2006-1542 and fix it if it is affected.

What it is: CVE-2006-1542 is a low-severity memory corruption vulnerability in Python Python, published on 30 Mar 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1542 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-2006-1542/ (Markdown: https://insights.sbomify.com/CVE-2006-1542/index.md)
```

## Sources

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

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