# CVE-2010-2425: Path traversal in n/a

> Authenticated remote attackers can read or delete arbitrary files via directory traversal in Titan FTP Server.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/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:** 23 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pqxh-2px8-rqhh

## What is CVE-2010-2425?

CVE-2010-2425 is a medium-severity path traversal vulnerability in n/a, published on 23 Jun 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in TitanFTPd in South River Technologies Titan FTP Server 8.10.1125, and probably earlier versions, allows remote authenticated users to read or delete arbitrary files via "..//" sequences in a COMB command.

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

## Which versions are affected by CVE-2010-2425?

It affects 1 product.


Products: Southrivertech Titan Ftp Server.

## How do I fix CVE-2010-2425?

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

## Is CVE-2010-2425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22629](https://insights.sbomify.com/CVE-2023-22629/): Path traversal in n/a (high 8.8)
- [CVE-2019-10009](https://insights.sbomify.com/CVE-2019-10009/): Path traversal in n/a (medium 6.5)
- [CVE-2022-44215](https://insights.sbomify.com/CVE-2022-44215/): Open redirect in n/a (medium 6.1)
- [CVE-2014-1841](https://insights.sbomify.com/CVE-2014-1841/): Path traversal in n/a (medium 5.0)
- [CVE-2014-1842](https://insights.sbomify.com/CVE-2014-1842/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2425 and fix it if it is affected.

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

## Sources

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

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