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

> Remote FTP servers can overwrite arbitrary files via directory traversal in Core FTP, potentially leading to code execution.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 3 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vmv8-824c-x53w

## What is CVE-2008-2519?

CVE-2008-2519 is a medium-severity path traversal vulnerability in n/a, published on 3 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 Core FTP client 2.1 Build 1565 allows remote FTP servers to create or overwrite arbitrary files via .. (dot dot) sequences in responses to LIST commands, a related issue to CVE-2002-1345.  NOTE: this can be leveraged for code execution by writing to a Startup folder.

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

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

It affects 1 product.


Products: Core Ftp Core Ftp.

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

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

## Is CVE-2008-2519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2519 is a medium-severity path traversal vulnerability in n/a, published on 3 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: There is no known exploitation of CVE-2008-2519 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-2008-2519/ (Markdown: https://insights.sbomify.com/CVE-2008-2519/index.md)
```

## Sources

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

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