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

> Local attackers can overwrite arbitrary files via symlink attacks on predictable log files in Mandrake Linux.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **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:** No
- **Published:** 14 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x5v5-9fj9-665w

## What is CVE-2002-2001?

CVE-2002-2001 is a low-severity path traversal vulnerability in Mandrakesoft Mandrake Linux, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

jmcce 1.3.8 in Mandrake 8.1 creates log files in /tmp with predictable names, which allows local users to overwrite arbitrary files via a symlink attack.

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

It affects 2 products.


Products: Jmcce Jmcce, Mandrakesoft Mandrake Linux.

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

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

## Is CVE-2002-2001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2001 is a low-severity path traversal vulnerability in Mandrakesoft Mandrake Linux, published on 14 Jul 2005. 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-2001 in the wild and no public exploit code.

Affected product: Mandrakesoft Mandrake Linux. 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-2001/ (Markdown: https://insights.sbomify.com/CVE-2002-2001/index.md)
```

## Sources

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

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