# CVE-2000-0574: Memory corruption in n/a

> Remote attackers can execute arbitrary commands or cause denial of service via format string vulnerabilities in FTP server setproctitle functions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8prx-m86f-2h6h

## What is CVE-2000-0574?

CVE-2000-0574 is a medium-severity memory corruption vulnerability in n/a, published on 19 Jul 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FTP servers such as OpenBSD ftpd, NetBSD ftpd, ProFTPd and Opieftpd do not properly cleanse untrusted format strings that are used in the setproctitle function (sometimes called by set_proc_title), which allows remote attackers to cause a denial of service or execute arbitrary commands.

## Which versions are affected by CVE-2000-0574?

It affects 2 products.


Products: Openbsd Ftpd, Washington University Wu-Ftpd.

## How do I fix CVE-2000-0574?

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

## Is CVE-2000-0574 being exploited?

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

Public exploit code:

- OpenBSD - 'ftp' Local Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0574 and fix it if it is affected.

What it is: CVE-2000-0574 is a medium-severity memory corruption vulnerability in n/a, published on 19 Jul 2000. 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-2000-0574 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-2000-0574/ (Markdown: https://insights.sbomify.com/CVE-2000-0574/index.md)
```

## Sources

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

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