# CVE-2004-2074: Denial of service in n/a

> Local users can crash the Dream FTP server by sending malicious format string specifiers in PASS or RETR commands.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3qh7-hqp3-w27g

## What is CVE-2004-2074?

CVE-2004-2074 is a medium-severity denial of service vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Format string vulnerability in Dream FTP 1.02 allows local users to cause a denial of service (crash) via format string specifiers in the (1) PASS or (2) RETR commands.

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

It affects 1 product.


Products: Bolintech Dream Ftp Server.

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

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

## Is CVE-2004-2074 being exploited?

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

Public exploit code:

- BolinTech DreamFTP Server 1.2 (1.02/TryFTP 1.0.0.1) - Remote User Name Format String (exploitdb)
- BolinTech Dream FTP Server 1.02 Format String (metasploit)
- BolinTech DreamFTP Server 1.02 - Format String (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0277](https://insights.sbomify.com/CVE-2004-0277/): Other in n/a (critical 10.0)
- [CVE-2006-6724](https://insights.sbomify.com/CVE-2006-6724/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2074 is a medium-severity denial of service vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2074 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-2074/ (Markdown: https://insights.sbomify.com/CVE-2004-2074/index.md)
```

## Sources

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

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