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

> Remote attackers can disrupt persistent TCP connections by injecting RST packets, exploiting large window sizes to guess sequence numbers.

- **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:** Yes
- **Published:** 5 May 2004
- **Updated:** 9 Oct 2026
- **Also known as:** DEBIAN-CVE-2004-0230, GHSA-58p6-7f25-xqv3, ROOT-OS-DEBIAN-12-CVE-2004-0230, ROOT-OS-DEBIAN-13-CVE-2004-0230

## What is CVE-2004-0230?

CVE-2004-0230 is a medium-severity denial of service vulnerability in Juniper Junos, published on 5 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TCP, when using a large Window Size, makes it easier for remote attackers to guess sequence numbers and cause a denial of service (connection loss) to persistent TCP connections by repeatedly injecting a TCP RST packet, especially in protocols that use long-lived connections, such as BGP.

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

It affects 12 products.


Products: Juniper Junos, Mcafee Network Data Loss Prevention, Microsoft Windows 2000, Microsoft Windows 98, Microsoft Windows 98se, Microsoft Windows Server 2003, Microsoft Windows Xp, Netbsd Netbsd, Openpgp Openpgp, Oracle Solaris, Xinuos Openserver, Xinuos Unixware.

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

Apply the vendor's patch.

## Is CVE-2004-0230 being exploited?

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

Public exploit code:

- Multiple Vendor - TCP Sequence Number Approximation (1) (exploitdb)
- Multiple Vendor - TCP Sequence Number Approximation (2) (exploitdb)
- Multiple Vendor - TCP Sequence Number Approximation (3) (exploitdb)
- Microsoft Windows XP/2000 - TCP Connection Reset (exploitdb)
- Multiple Vendor - TCP Sequence Number Approximation (4) (exploitdb)
- TCP Connection Reset - Remote Denial of Service (exploitdb)

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0230 is a medium-severity denial of service vulnerability in Juniper Junos, published on 5 May 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-0230 exists.

Affected product: Juniper Junos. 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-0230/ (Markdown: https://insights.sbomify.com/CVE-2004-0230/index.md)
```

## Sources

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

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