# CVE-2002-1139: Path traversal in n/a

> Attackers can exploit ZIP decompression flaws to place executables in sensitive locations, potentially leading to code execution on Windows systems.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3c6p-m5wm-96c3

## What is CVE-2002-1139?

CVE-2002-1139 is a medium-severity path traversal vulnerability in Microsoft Windows Me, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Compressed Folders feature in Microsoft Windows 98 with Plus! Pack, Windows Me, and Windows XP does not properly check the destination folder during the decompression of ZIP files, which allows attackers to place an executable file in a known location on a user's system, aka "Incorrect Target Path for Zipped File Decompression."

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

It affects 3 products.


Products: Microsoft Windows 98 Plus Pack, Microsoft Windows Me, Microsoft Windows Xp.

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

No fix has been published for CVE-2002-1139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-1139 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1139 and fix it if it is affected.

What it is: CVE-2002-1139 is a medium-severity path traversal vulnerability in Microsoft Windows Me, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1139 in the wild and no public exploit code.

Affected product: Microsoft Windows Me. 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-1139/ (Markdown: https://insights.sbomify.com/CVE-2002-1139/index.md)
```

## Sources

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

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