# CVE-2005-0520: Path traversal in n/a

> Remote attackers can read arbitrary files on ArGoSoft FTP Server via shortcut files in the SITE COPY command.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r9mg-cpxj-xx85

## What is CVE-2005-0520?

CVE-2005-0520 is a critical path traversal vulnerability in n/a, published on 23 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArGoSoft FTP Server before 1.4.2.8 allows remote attackers to read arbitrary files via shortcut (.LNK) files in the SITE COPY command, a different vulnerability than CVE-2005-0519.

## Which versions are affected by CVE-2005-0520?

It affects 1 product.


Products: Argosoft Ftp Server.

## How do I fix CVE-2005-0520?

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

## Is CVE-2005-0520 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0519](https://insights.sbomify.com/CVE-2005-0519/): Path traversal in n/a (critical 10.0)
- [CVE-2004-2673](https://insights.sbomify.com/CVE-2004-2673/): Memory corruption in n/a (critical 9.0)
- [CVE-2004-2672](https://insights.sbomify.com/CVE-2004-2672/): File upload in n/a (high 7.5)
- [CVE-2005-0696](https://insights.sbomify.com/CVE-2005-0696/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1429](https://insights.sbomify.com/CVE-2004-1429/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0520 and fix it if it is affected.

What it is: CVE-2005-0520 is a critical path traversal vulnerability in n/a, published on 23 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0520 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-2005-0520/ (Markdown: https://insights.sbomify.com/CVE-2005-0520/index.md)
```

## Sources

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

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