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

> Remote attackers can execute arbitrary code on BlackJumboDog FTP servers by sending long commands, requiring immediate patching.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 13 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9r3x-fhpw-xh4j

## What is CVE-2004-1439?

CVE-2004-1439 is a high-severity memory corruption vulnerability in n/a, published on 13 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in BlackJumboDog 3.x allows remote attackers to execute arbitrary code via long FTP commands such as (1) USER, (2) PASS, (3) RETR,(4) CWD, (5) XMKD, and (6) XRMD.

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

It affects 1 product.


Products: Sapporoworks Black Jumbodog.

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

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

## Is CVE-2004-1439 being exploited?

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

Public exploit code:

- BlackJumboDog FTP Server - Remote Buffer Overflow (exploitdb)
- BlackJumboDog FTP Server 3.6.1 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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