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

> Attackers can overwrite arbitrary files during archive extraction via directory traversal strings, requiring user interaction to extract the malicious archive.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Oct 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-c6fq-h555-8326

## What is CVE-2002-0399?

CVE-2002-0399 is a medium-severity path traversal vulnerability in n/a, published on 1 Oct 2002. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in GNU tar 1.13.19 through 1.13.25, and possibly later versions, allows attackers to overwrite arbitrary files during archive extraction via a (1) "/.." or (2) "./.." string, which removes the leading slash but leaves the "..", a variant of CVE-2001-1267.

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

It affects 1 product.


Products: Gnu Tar.

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

Upgrade to a fixed version.

## Is CVE-2002-0399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2541](https://insights.sbomify.com/CVE-2005-2541/): Privilege escalation in n/a (critical 10.0)
- [CVE-2019-9923](https://insights.sbomify.com/CVE-2019-9923/): Null dereference in n/a (high 7.5)
- [CVE-2016-6321](https://insights.sbomify.com/CVE-2016-6321/): Path traversal in n/a (high 7.5)
- [CVE-2007-4131](https://insights.sbomify.com/CVE-2007-4131/): Path traversal in n/a (medium 6.8)
- [CVE-2023-39804](https://insights.sbomify.com/CVE-2023-39804/): Denial of service in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0399 is a medium-severity path traversal vulnerability in n/a, published on 1 Oct 2002. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0399 in the wild and no public exploit code.

Affected product: n/a. 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-0399/ (Markdown: https://insights.sbomify.com/CVE-2002-0399/index.md)
```

## Sources

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

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