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

> Remote attackers can disrupt TCP connections by sending spoofed ICMP error messages, causing a 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:** 13 Apr 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5c86-xw43-gw75

## What is CVE-2004-0790?

CVE-2004-0790 is a medium-severity denial of service vulnerability in Microsoft Windows 2000, published on 13 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple TCP/IP and ICMP implementations allow remote attackers to cause a denial of service (reset TCP connections) via spoofed ICMP error messages, aka the "blind connection-reset attack."  NOTE: CVE-2004-0790, CVE-2004-0791, and CVE-2004-1060 have been SPLIT based on different attacks; CVE-2005-0065, CVE-2005-0066, CVE-2005-0067, and CVE-2005-0068 are related identifiers that are SPLIT based on the underlying vulnerability.  While CVE normally SPLITs based on vulnerability, the attack-based identifiers exist due to the variety and number of affected implementations and solutions that address the attacks instead of the underlying vulnerabilities.

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

It affects 8 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows 98, Microsoft Windows 98se, Microsoft Windows Me, Microsoft Windows Xp, Sun Solaris, Sun Sunos.

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

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

## Is CVE-2004-0790 being exploited?

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

Public exploit code:

- Multiple Vendor ICMP Message Handling - Denial of Service (exploitdb)
- Microsoft Windows - Malformed IP Options Denial of Service (MS05-019) (exploitdb)
- Multiple OS (Win32/Aix/Cisco) - Crafted ICMP Messages Denial of Service (MS05-019) (exploitdb)

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0790 is a medium-severity denial of service vulnerability in Microsoft Windows 2000, published on 13 Apr 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-0790 exists.

Affected product: Microsoft Windows 2000. 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-0790/ (Markdown: https://insights.sbomify.com/CVE-2004-0790/index.md)
```

## Sources

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

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