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

> Remote FTP servers can write arbitrary files via directory traversal in Robo-FTP, requiring user connection to a malicious server.

- **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:** 26 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-56gm-vr9p-4jrr

## What is CVE-2010-4095?

CVE-2010-4095 is a critical path traversal vulnerability in n/a, published on 26 Oct 2010. 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 Serengeti Systems Incorporated Robo-FTP 3.7.3, and probably other versions before 3.7.5, allows remote FTP servers to write arbitrary files via a .. (dot dot) in a filename in a server response.

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

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

It affects 1 product.


Products: Robo-Ftp Robo-Ftp.

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

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

## Is CVE-2010-4095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4103](https://insights.sbomify.com/CVE-2009-4103/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4095 is a critical path traversal vulnerability in n/a, published on 26 Oct 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-4095 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-4095/ (Markdown: https://insights.sbomify.com/CVE-2010-4095/index.md)
```

## Sources

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

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