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

> Remote attackers can execute arbitrary code on Netcat for Windows instances running with the -e option via a stack-based buffer overflow.

- **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:** 31 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wppp-w39w-5fq5

## What is CVE-2004-1317?

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

### Official description

Stack-based buffer overflow in doexec.c in Netcat for Windows 1.1, when running with the -e option, allows remote attackers to execute arbitrary code via a long DNS command.

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


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

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

## Is CVE-2004-1317 being exploited?

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

Public exploit code:

- Netcat 1.1 - '-e' Switch Remote Buffer Overflow (exploitdb)
- Netcat v1.10 NT Stack Buffer Overflow (metasploit)
- Netcat 1.10 - NT Stack Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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