CVE-2004-0790

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has 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.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
5.0EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 80%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 80%CVSS v2: 5.0Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

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

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation80% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
80%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 12, 2005

Last Modified

June 16, 2026

References (54)

Data Freshness Timeline

(refreshed 1× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-29 02:40 UTCEG score recompute
  2. 2026-09-12 14:54 UTCEPSS rescore
  3. 2026-09-10 09:23 UTCEPSS rescore
  4. 2026-07-26 13:24 UTCEG score recompute▲ 5.00
  5. 2026-07-24 14:11 UTCEPSS rescore
  6. 2026-07-23 00:46 UTCEG score recompute
  7. 2026-07-23 00:27 UTCEG score recompute▼ 8.20
  8. 2026-07-22 23:50 UTCEG score recompute▲ 8.20
  9. 2026-07-22 21:30 UTCEG score recompute▼ 9.00
  10. 2026-07-20 17:02 UTCEPSS rescore
  11. 2026-07-16 16:58 UTCEPSS rescore
  12. 2026-07-04 06:26 UTCEPSS rescore
  13. 2026-06-28 04:52 UTCEPSS rescore
  14. 2026-06-23 21:29 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-16 17:49 UTCEPSS rescore
  20. 2026-06-15 17:43 UTCEPSS rescore
  21. 2026-06-14 23:13 UTCEPSS rescore
  22. 2026-06-14 23:13 UTCEPSS rescore
  23. 2026-06-13 22:56 UTCEPSS rescore
  24. 2026-06-12 23:08 UTCEPSS rescore
  25. 2026-06-10 22:13 UTCEPSS rescore
Show 25 more
  1. 2026-06-10 13:17 UTCEPSS rescore
  2. 2026-06-08 14:13 UTCEPSS rescore
  3. 2026-06-07 15:21 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-06 13:44 UTCEPSS rescore
  6. 2026-06-06 13:44 UTCEPSS rescore
  7. 2026-06-05 22:43 UTCEPSS rescore
  8. 2026-06-05 22:43 UTCEPSS rescore
  9. 2026-05-31 22:28 UTCEPSS rescore
  10. 2026-05-31 14:08 UTCEG score recompute
  11. 2026-05-31 14:08 UTCGHSA enrichment
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-31 00:13 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-27 13:37 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-20 22:36 UTCEPSS rescore
  22. 2026-05-20 11:20 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-948✓ verified
    First seen Apr 20, 2005

    Multiple OS (Win32/Aix/Cisco) - Crafted ICMP Messages Denial of Service (MS05-019)

    Open source ↗
  • Exploit-DBEDB-942✓ verified
    First seen Apr 17, 2005

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

    Open source ↗
  • Exploit-DBEDB-25389✓ verified
    First seen Apr 12, 2005

    Multiple Vendor ICMP Message Handling - Denial of Service

    Open source ↗

Frequently asked(4)

What is CVE-2004-0790?
CVE-2004-0790 is a medium vulnerability published on April 12, 2005. 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;…
When was CVE-2004-0790 disclosed?
CVE-2004-0790 was first published on April 12, 2005, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-0790 actively exploited?
CVE-2004-0790 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. 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-0790?
No fix for CVE-2004-0790 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2004-0790

Explore →

Is Your Infrastructure Affected by CVE-2004-0790?

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

Book a Demo →Browse All CVEs