# CVE-2004-2037: Memory corruption in n/a

> Remote authenticated users can trigger a buffer overflow via a long CWD command, causing a crash or potential arbitrary code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p65m-pc6q-hg8v

## What is CVE-2004-2037?

CVE-2004-2037 is a high-severity memory corruption vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Mollensoft Lightweight FTP Server 3.6 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via a long CWD command, as demonstrated in one example by using the "cd" command in an interactive FTP client.

## Which versions are affected by CVE-2004-2037?

It affects 1 product.


Products: Mollensoft Software Lightweight Ftp Server.

## How do I fix CVE-2004-2037?

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

## Is CVE-2004-2037 being exploited?

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

Public exploit code:

- Mollensoft Lightweight FTP Server 3.6 - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2037 and fix it if it is affected.

What it is: CVE-2004-2037 is a high-severity memory corruption vulnerability in n/a, published on 10 May 2005. 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-2004-2037 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-2004-2037/ (Markdown: https://insights.sbomify.com/CVE-2004-2037/index.md)
```

## Sources

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

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