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

> Local attackers can gain privileges by manipulating the PATH environment variable to execute a malicious gzip binary via LuxMan.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** DSA-189, GHSA-5cc9-22f6-38c6

## What is CVE-2002-1245?

CVE-2002-1245 is a high-severity path traversal vulnerability in n/a, 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

Maped in LuxMan 0.41 uses the user-provided search path to find and execute the gzip program, which allows local users to modify /dev/mem and gain privileges via a modified PATH environment variable that points to a Trojan horse gzip program.

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

It affects 1 product.


Products: Frank Mcingvale Luxman.

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

Apply the vendor's patch.

## Is CVE-2002-1245 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0385](https://insights.sbomify.com/CVE-2005-0385/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1245 is a high-severity path traversal vulnerability in n/a, 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-1245 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-1245/ (Markdown: https://insights.sbomify.com/CVE-2002-1245/index.md)
```

## Sources

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

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