CVE-2004-0230

MEDIUMCVSS v2 · 5.05.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — NVD rates that MEDIUM (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 80% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized

Also known asEUVD-2004-0230 (ENISA EUVD) · GHSA-58p6-7f25-xqv3 (GitHub Security Advisories)Source: ENISA EUVD

5.0EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 80%
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 80%CVSS v2: 5.0Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity50% × 45%
Impact severity (EG Severity): CVSS 5.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation80% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
80%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.

EG Severity
5.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:N/I:N/A:P
EG Likelihood
80% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2004

Last Modified

October 9, 2026

References (29)

15 of 29 shown · show the other 14

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc6-1~exp1 (361 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.3~rc6-1~exp1 (184 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.3~rc6-1~exp1 (184 versions)
  • every version on: no fix on record
—

Data Freshness Timeline

(refreshed 5× in last 7d / 20× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 67 is merged into the row it repeats.

  1. 2026-11-21 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  2. 2026-11-20 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  3. 2026-11-19 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  4. 2026-11-18 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  5. 2026-11-16 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  6. 2026-11-15 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  7. 2026-11-11 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  8. 2026-11-10 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  9. 2026-11-08 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  10. 2026-11-08 02:47 UTCGHSA enrichmentGHSA-58p6-7f25-xqv3 · GitHub severity MODERATE
  11. 2026-11-08 02:47 UTCEchelonGraph re-scored
  12. 2026-11-04 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  13. 2026-11-03 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  14. 2026-10-31 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  15. 2026-10-29 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  16. 2026-10-29 14:22 UTCEchelonGraph re-scored
  17. 2026-10-29 14:22 UTCGHSA enrichmentGHSA-58p6-7f25-xqv3
  18. 2026-10-27 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  19. 2026-10-27 06:25 UTCOSV refresh
  20. 2026-10-26 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  21. 2026-10-25 20:51 UTCEchelonGraph re-scored
  22. 2026-10-25 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  23. 2026-10-24 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  24. 2026-10-22 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
  25. 2026-10-21 16:24 UTCEPSS rescoreEPSS 80% · 99th percentile
Show 41 more
  1. 2026-10-19 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  2. 2026-10-18 12:20 UTCEchelonGraph re-scored
  3. 2026-10-15 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  4. 2026-10-14 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  5. 2026-10-13 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  6. 2026-10-12 22:17 UTCEchelonGraph re-scored
  7. 2026-10-12 16:25 UTCEPSS rescoreEPSS 80% · 99th percentile
  8. 2026-10-12 02:23 UTCEchelonGraph re-scored
  9. 2026-10-09 20:34 UTCGHSA enrichmentGHSA-58p6-7f25-xqv3
  10. 2026-10-09 20:33 UTCNVD update
  11. 2026-10-09 19:58 UTCEPSS rescoreEPSS 80% · 99th percentile
  12. 2026-10-09 19:19 UTCEchelonGraph re-scored
  13. 2026-10-09 19:19 UTCGHSA enrichmentGHSA-58p6-7f25-xqv3
  14. 2026-10-09 19:18 UTCMITRE cvelistV5
  15. 2026-10-07 23:54 UTCOSV refresh
  16. 2026-10-07 23:35 UTCEPSS rescoreEPSS 80% · 99th percentile
  17. 2026-10-05 17:36 UTCEPSS rescoreEPSS 80% · 99th percentile
  18. 2026-09-29 02:39 UTCEchelonGraph re-scored
  19. 2026-09-18 05:50 UTCOSV refresh
  20. 2026-09-12 14:54 UTCEPSS rescoreEPSS 80% · 99th percentile
  21. 2026-09-10 09:23 UTCEPSS rescoreEPSS 80% · 99th percentile
  22. 2026-08-30 06:07 UTCOSV refresh
  23. 2026-08-30 01:13 UTCEPSS rescoreEPSS 80% · 99th percentile
  24. 2026-08-13 21:51 UTCOSV refresh
  25. 2026-07-29 00:47 UTCOSV refresh
  26. 2026-07-26 13:24 UTCEchelonGraph re-scoredAssessed again: 5.0 MEDIUM
  27. 2026-07-24 14:11 UTCEPSS rescoreEPSS 80% · 99th percentile
  28. 2026-07-23 00:45 UTCEchelonGraph re-scored
  29. 2026-07-23 00:27 UTCEchelonGraph re-scored▼ 8.20
  30. 2026-07-22 23:50 UTCEchelonGraph re-scoredFirst assessed: 8.2 HIGH
  31. 2026-07-22 21:30 UTCEchelonGraph re-scored
  32. 2026-07-20 17:02 UTCEPSS rescoreEPSS 80% · 99th percentile
  33. 2026-07-15 01:55 UTCEPSS rescoreEPSS 81% · 99th percentile
  34. 2026-07-11 17:22 UTCOSV refresh
  35. 2026-07-06 02:19 UTCEPSS rescoreEPSS 81% · 99th percentile
  36. 2026-07-02 14:00 UTCEPSS rescoreEPSS 81% · 99th percentile
  37. 2026-06-27 03:04 UTCEPSS rescoreEPSS 81% · 99th percentile
  38. 2026-06-23 21:29 UTCEPSS rescoreEPSS 81% · 99th percentile
  39. 2026-06-22 23:59 UTCEchelonGraph re-scored
  40. 2026-06-22 23:59 UTCGHSA enrichmentGHSA-58p6-7f25-xqv3
  41. 2026-06-22 23:58 UTCNVD updatefirst tracked

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (7 Exploit-DB entries). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-942✓ verified
    Published Apr 17, 2005

    Microsoft Windows - Malformed IP Options Denial of Service (MS05-019)

    Open source ↗
  • Exploit-DBEDB-24033✓ verified
    Published Apr 23, 2004

    Multiple Vendor - TCP Sequence Number Approximation (4)

    Open source ↗
  • Exploit-DBEDB-291✓ verified
    Published Apr 23, 2004

    TCP Connection Reset - Remote Denial of Service

    Open source ↗
  • Exploit-DBEDB-276✓ verified
    Published Apr 22, 2004

    Microsoft Windows XP/2000 - TCP Connection Reset

    Open source ↗
  • Exploit-DBEDB-24031✓ verified
    Published Apr 20, 2004

    Multiple Vendor - TCP Sequence Number Approximation (2)

    Open source ↗
  • Exploit-DBEDB-24032✓ verified
    Published Apr 20, 2004

    Multiple Vendor - TCP Sequence Number Approximation (3)

    Open source ↗
  • Exploit-DBEDB-24030✓ verified
    Published Mar 5, 2004

    Multiple Vendor - TCP Sequence Number Approximation (1)

    Open source ↗

Frequently asked(4)

What is CVE-2004-0230?
CVE-2004-0230 is a medium-severity vulnerability; its CVE record was published on August 18, 2004. 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.
When was CVE-2004-0230 made public?
CVE-2004-0230 was made public on April 20, 2004: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 18, 2004. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2004-0230 actively exploited?
CVE-2004-0230 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 80% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-0230?
A fix for CVE-2004-0230 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-0230

Explore →

Is Your Infrastructure Affected by CVE-2004-0230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.