# CVE-2001-0053: Memory corruption in n/a

> Remote attackers can exploit a buffer overflow in BSD ftpd to gain root privileges, requiring immediate patching of the FTP server.

- **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:** 7 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-286p-cf2h-fc7g

## What is CVE-2001-0053?

CVE-2001-0053 is a critical memory corruption vulnerability in Netbsd Netbsd, published on 7 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

One-byte buffer overflow in replydirname function in BSD-based ftpd allows remote attackers to gain root privileges.

## Which versions are affected by CVE-2001-0053?

It affects 3 products.


Products: David Madore Ftpd-Bsd, Netbsd Netbsd, Openbsd Openbsd.

## How do I fix CVE-2001-0053?

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

## Is CVE-2001-0053 being exploited?

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

Public exploit code:

- BSD ftpd 0.3.2 - Single Byte Buffer Overflow (exploitdb)
- OpenBSD ftpd 2.6/2.7 - Remote Overflow (exploitdb)

## Other vulnerabilities in Netbsd Netbsd

- [CVE-2001-0550](https://insights.sbomify.com/CVE-2001-0550/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0053 and fix it if it is affected.

What it is: CVE-2001-0053 is a critical memory corruption vulnerability in Netbsd Netbsd, published on 7 May 2001. 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-2001-0053 exists.

Affected product: Netbsd Netbsd. 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-2001-0053/ (Markdown: https://insights.sbomify.com/CVE-2001-0053/index.md)
```

## Sources

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

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