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

> Attackers can read file attributes outside the web root via FTP commands if relative path display is disabled.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 24 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9xm5-646v-mfcw

## What is CVE-2001-0263?

CVE-2001-0263 is a high-severity path traversal vulnerability in n/a, published on 24 May 2001. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gene6 G6 FTP Server 2.0 (aka BPFTP Server 2.10) allows attackers to read file attributes outside of the web root via the (1) SIZE and (2) MDTM commands when the "show relative paths" option is not enabled.

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

It affects 1 product.


Products: Gene6 G6 Ftp Server.

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

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

## Is CVE-2001-0263 being exploited?

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

Public exploit code:

- Gene6 BPFTP Server 2.0 - File Existence Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-2172](https://insights.sbomify.com/CVE-2006-2172/): Memory corruption in n/a (high 7.5)
- [CVE-1999-1519](https://insights.sbomify.com/CVE-1999-1519/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0264](https://insights.sbomify.com/CVE-2001-0264/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-0690](https://insights.sbomify.com/CVE-2005-0690/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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