# CVE-2008-2894: Path traversal in n/a

> Remote FTP servers can overwrite arbitrary files on the client system via directory traversal in LIST responses, requiring user interaction to connect.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ffhc-mxrh-vv2p

## What is CVE-2008-2894?

CVE-2008-2894 is a critical path traversal vulnerability in n/a, published on 27 Jun 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in the FTP client in NCH Software Classic FTP 1.02 for Windows allows remote FTP servers to create or overwrite arbitrary files via a .. (dot dot) in a response to a LIST command, a related issue to CVE-2002-1345.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2008-2894?

It affects 1 product.


Products: Nch Software Nch Software Classic Ftp.

## How do I fix CVE-2008-2894?

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

## Is CVE-2008-2894 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2894 exists.

Public exploit code:

- Classic FTP 1.02 - 'LIST' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2894 and fix it if it is affected.

What it is: CVE-2008-2894 is a critical path traversal vulnerability in n/a, published on 27 Jun 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2894 exists.

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-2008-2894/ (Markdown: https://insights.sbomify.com/CVE-2008-2894/index.md)
```

## Sources

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

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