CVE-2003-0001

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:P/I:N/A:N. 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 70.0% 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 verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 70%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 70%CVSS v2: 5.0Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Multiple ethernet Network Interface Card (NIC) device drivers do not pad frames with null bytes, which allows remote attackers to obtain information from previous packets or kernel memory by using malformed packets, as demonstrated by Etherleak.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

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%
Exploitation70% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
70%
EPSS %ILE
99%
KEV
Not listed

Published

January 17, 2003

Last Modified

June 16, 2026

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2003-06-25redhat
redhatpatch2003-03-20redhat
redhatpatch2003-02-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 17× 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-07-26 13:23 UTCEG score recompute 5.00
  2. 2026-07-25 14:11 UTCEPSS rescore
  3. 2026-07-24 14:11 UTCEPSS rescore
  4. 2026-07-23 00:45 UTCEG score recompute
  5. 2026-07-23 00:26 UTCEG score recompute 6.60
  6. 2026-07-22 23:49 UTCEG score recompute 6.60
  7. 2026-07-22 21:29 UTCEG score recompute
  8. 2026-07-20 17:02 UTCEPSS rescore
  9. 2026-07-18 09:59 UTCEPSS rescore
  10. 2026-07-18 09:59 UTCEPSS rescore
  11. 2026-07-16 16:58 UTCEPSS rescore
  12. 2026-07-13 06:07 UTCEPSS rescore
  13. 2026-07-11 08:22 UTCEPSS rescore
  14. 2026-07-11 08:22 UTCEPSS rescore
  15. 2026-07-04 06:26 UTCEPSS rescore
  16. 2026-06-28 14:02 UTCEPSS rescore
  17. 2026-06-28 04:52 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-16 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
Show 39 more
  1. 2026-06-15 17:43 UTCEPSS rescore
  2. 2026-06-14 23:13 UTCEPSS rescore
  3. 2026-06-14 23:13 UTCEPSS rescore
  4. 2026-06-13 22:56 UTCEPSS rescore
  5. 2026-06-12 23:08 UTCEPSS rescore
  6. 2026-06-11 13:55 UTCEPSS rescore
  7. 2026-06-10 22:13 UTCEPSS rescore
  8. 2026-06-10 13:17 UTCEPSS rescore
  9. 2026-06-06 13:44 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-06 13:44 UTCEPSS rescore
  12. 2026-06-05 22:43 UTCEPSS rescore
  13. 2026-06-05 22:43 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-05-31 22:28 UTCEPSS rescore
  20. 2026-05-31 17:55 UTCEG score recompute
  21. 2026-05-31 17:55 UTCVendor advisory
  22. 2026-05-31 17:55 UTCGHSA enrichment
  23. 2026-05-31 00:13 UTCEPSS rescore
  24. 2026-05-31 00:13 UTCEPSS rescore
  25. 2026-05-29 13:40 UTCEPSS rescore
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-27 13:37 UTCEPSS rescore
  31. 2026-05-26 07:16 UTCEPSS rescore
  32. 2026-05-26 07:16 UTCEPSS rescore
  33. 2026-05-24 16:42 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-20 22:36 UTCEPSS rescore
  36. 2026-05-20 11:20 UTCEPSS rescore
  37. 2026-05-20 11:20 UTCEPSS rescore
  38. 2026-05-18 21:29 UTCEPSS rescore
  39. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

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

  • GitHub PoCmarb08/etherleak-checker
    First seen Oct 1, 2024

    This Python script helps to detect the Etherleak (CVE-2003-0001) vulnerability on a target host by analyzing the padding data in network packets. The script uses Scapy to send various types of requests (ICMP, ARP, or TCP) and checks if the responses contain any padding data that could potentially leak sensitive memory contents.

    Open source ↗
  • Exploit-DBEDB-26076
    First seen Jun 10, 2013

    Cisco ASA < 8.4.4.6 < 8.2.5.32 - Ethernet Information Leak

    Open source ↗
  • Exploit-DBEDB-22131✓ verified
    First seen Mar 23, 2007

    Linux Kernel 2.0.x/2.2.x/2.4.x (FreeBSD 4.x) - Network Device Driver Frame Padding Information Disclosure

    Open source ↗
  • Exploit-DBEDB-3555✓ verified
    First seen Mar 23, 2007

    Ethernet Device Drivers Frame Padding - 'Etherleak' Infomation Leakage

    Open source ↗

Frequently asked(4)

What is CVE-2003-0001?
CVE-2003-0001 is a medium vulnerability published on January 17, 2003. Multiple ethernet Network Interface Card (NIC) device drivers do not pad frames with null bytes, which allows remote attackers to obtain information from previous packets or kernel memory by using malformed packets, as demonstrated by Etherleak.
When was CVE-2003-0001 disclosed?
CVE-2003-0001 was first published in the National Vulnerability Database on January 17, 2003, 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-2003-0001 actively exploited?
CVE-2003-0001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
How do I remediate CVE-2003-0001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-0001, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2003-0001

Explore →

Is Your Infrastructure Affected by CVE-2003-0001?

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