# CVE-2004-2594: Path traversal in n/a

> Remote attackers can read arbitrary files on Quake II Windows servers via path traversal in download arguments.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4839-775x-j3vf

## What is CVE-2004-2594?

CVE-2004-2594 is a medium-severity path traversal vulnerability in n/a, published on 29 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in Quake II server before R1Q2 on Windows, as used in multiple products, allows remote attackers to read arbitrary files via a "\/" in a pathname argument, as demonstrated by "download \/server.cfg".

## Which versions are affected by CVE-2004-2594?

It affects 1 product.


Products: Id Software Quake Ii Server Windows.

## How do I fix CVE-2004-2594?

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

## Is CVE-2004-2594 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2594 and fix it if it is affected.

What it is: CVE-2004-2594 is a medium-severity path traversal vulnerability in n/a, published on 29 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2594 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-2004-2594/ (Markdown: https://insights.sbomify.com/CVE-2004-2594/index.md)
```

## Sources

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

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