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

> Remote FTP servers can crash CuteFTP Professional via buffer overflow in large command replies, causing denial of service.

- **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:** 8 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9gfv-rpw5-mwc9

## What is CVE-2004-1136?

CVE-2004-1136 is a medium-severity memory corruption vulnerability in n/a, published on 8 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in CuteFTP Professional 6.0, and possibly other versions, allows remote FTP servers to cause a denial of service (application crash) via large replies to FTP commands.

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

It affects 1 product.


Products: Globalscape Cuteftp.

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

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

## Is CVE-2004-1136 being exploited?

There is no known exploitation of CVE-2004-1136 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2009-3483](https://insights.sbomify.com/CVE-2009-3483/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-2779](https://insights.sbomify.com/CVE-2008-2779/): Path traversal in n/a (critical 9.3)
- [CVE-2003-1260](https://insights.sbomify.com/CVE-2003-1260/): Memory corruption in n/a (high 7.6)
- [CVE-2000-0084](https://insights.sbomify.com/CVE-2000-0084/): Weak cryptography in n/a (medium 5.0)
- [CVE-2024-1190](https://insights.sbomify.com/CVE-2024-1190/): Global Scape CuteFTP denial of service (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1136 is a medium-severity memory corruption vulnerability in n/a, published on 8 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1136 in the wild and no public exploit code.

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-1136/ (Markdown: https://insights.sbomify.com/CVE-2004-1136/index.md)
```

## Sources

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

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