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

> Remote attackers can list arbitrary directories on FaSTream FTP++ Server by including drive letters in pathnames, exposing file system structure.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/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:** 4 Apr 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6pv3-758h-9wgc

## What is CVE-2001-0255?

CVE-2001-0255 is a medium-severity path traversal vulnerability in n/a, published on 4 Apr 2001. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FaSTream FTP++ Server 2.0 allows remote attackers to list arbitrary directories by using the "ls" command and including the drive letter name (e.g. C:) in the requested pathname.

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

It affects 2 products.


Products: Fastream Fastream Ftp\+\+ Server, Fastream Fastream Ftp Server.

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

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

## Is CVE-2001-0255 being exploited?

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

Public exploit code:

- fastream ftp++ 2.0 - Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0255 is a medium-severity path traversal vulnerability in n/a, published on 4 Apr 2001. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0255 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-2001-0255/ (Markdown: https://insights.sbomify.com/CVE-2001-0255/index.md)
```

## Sources

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

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