# CVE-2005-3524: Memory corruption in n/a

> Remote attackers can execute arbitrary code on linux-ftpd-ssl by exploiting a buffer overflow via a long directory name in the XPWD 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:** Yes
- **Published:** 7 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3524, DSA-896-1, GHSA-23wf-343v-3cqg

## What is CVE-2005-3524?

CVE-2005-3524 is a critical memory corruption vulnerability in n/a, published on 7 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the SSL-ready version of linux-ftpd (linux-ftpd-ssl) 0.17 allows remote attackers to execute arbitrary code by creating a long directory name, then executing the XPWD command.

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

It affects 1 product.


Products: Linux-Ftpd-Ssl Linux-Ftpd-Ssl.

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

Apply the vendor's patch.

## Is CVE-2005-3524 being exploited?

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

Public exploit code:

- linux-ftpd-ssl 0.17 - 'MKD'/'CWD' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5778](https://insights.sbomify.com/CVE-2006-5778/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3524 is a critical memory corruption vulnerability in n/a, published on 7 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3524 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-2005-3524/ (Markdown: https://insights.sbomify.com/CVE-2005-3524/index.md)
```

## Sources

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

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