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

> Authenticated remote attackers can read or list arbitrary files on Nexgen FTP Server via directory traversal in FTP commands.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vwvq-g57j-fg4q

## What is CVE-2004-2488?

CVE-2004-2488 is a medium-severity path traversal vulnerability in n/a, published on 25 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Nexgen FTP Server before 2.2.3.23 allows remote authenticated users to read or list arbitrary files via "C:" sequences in the (1) RETR (get), (2) NLST (ls), (3) LIST (ls), (4) RNFR, or (5) RNTO FTP commands.

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


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

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

## Is CVE-2004-2488 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2488 is a medium-severity path traversal vulnerability in n/a, published on 25 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2488 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-2488/ (Markdown: https://insights.sbomify.com/CVE-2004-2488/index.md)
```

## Sources

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

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