# CVE-2002-1119: Race condition in n/a

> Local attackers can execute arbitrary code via symlink attacks on predictable temporary files in Python's os module.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** AZL-109542, DSA-159, GHSA-v59x-92cq-qv2v

## What is CVE-2002-1119?

CVE-2002-1119 is a medium-severity vulnerability in Python Python, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

os._execvpe from os.py in Python 2.2.1 and earlier creates temporary files with predictable names, which could allow local users to execute arbitrary code via a symlink attack.

## Which versions are affected by CVE-2002-1119?

It affects 1 product.


Products: Python Python.

## How do I fix CVE-2002-1119?

Upgrade to a fixed version.

## Is CVE-2002-1119 being exploited?

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

What it is: CVE-2002-1119 is a medium-severity vulnerability in Python Python, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1119 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-2002-1119/ (Markdown: https://insights.sbomify.com/CVE-2002-1119/index.md)
```

## Sources

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

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