# CVE-2009-5141: Other in n/a

> Authenticated remote attackers can crash the War FTP Daemon via format string specifiers in the LIST command.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2xwc-ff9j-7r5h

## What is CVE-2009-5141?

CVE-2009-5141 is a medium-severity vulnerability in n/a, published on 1 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Format string vulnerability in War FTP Daemon (warftpd) 1.82 RC 12 allows remote authenticated users to cause a denial of service (crash) via format string specifiers in a LIST command.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2009-5141?

It affects 1 product.


Products: Jgaa Warftpd.

## How do I fix CVE-2009-5141?

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

## Is CVE-2009-5141 being exploited?

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

Public exploit code:

- WarFTPd 1.82.00-RC12 - 'LIST' Format String Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-2278](https://insights.sbomify.com/CVE-2013-2278/): Denial of service in n/a (critical 10.0)
- [CVE-2000-0044](https://insights.sbomify.com/CVE-2000-0044/): Command injection in n/a (critical 10.0)
- [CVE-1999-0256](https://insights.sbomify.com/CVE-1999-0256/): Memory corruption in n/a (high 7.5)
- [CVE-2006-2171](https://insights.sbomify.com/CVE-2006-2171/): Memory corruption in n/a (medium 6.4)
- [CVE-2000-0131](https://insights.sbomify.com/CVE-2000-0131/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5141 and fix it if it is affected.

What it is: CVE-2009-5141 is a medium-severity vulnerability in n/a, published on 1 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5141 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-2009-5141/ (Markdown: https://insights.sbomify.com/CVE-2009-5141/index.md)
```

## Sources

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

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