CVE-2003-1013

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 4.5%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

The Q.931 dissector in Ethereal before 0.10.0, and Tethereal, allows remote attackers to cause a denial of service (crash) via a malformed Q.931, which triggers a null dereference.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
84.5%
KEV
Not listed

Published

January 5, 2004

Last Modified

June 16, 2026

Advisory Details (6)

Auto-updated May 31, 2026
No patch confirmed yet.
generic

Support

http://www.redhat.com/support/errata/RHSA-2004-001.html
generic
http://www.ethereal.com/appnotes/enpa-sa-00012.html
generic

Debian -- The Universal Operating System

http://www.debian.org/security/2003/dsa-407
generic

About Secunia Research | Flexera

http://secunia.com/advisories/10570
generic

About Secunia Research | Flexera

http://secunia.com/advisories/10568
generic

About Secunia Research | Flexera

http://secunia.com/advisories/10531

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatethereal-0:0.10.0a-0.30E.12004-01-20redhat
redhatpatch2004-01-07redhat

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

(2)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2003-1013?
CVE-2003-1013 is a high vulnerability published on January 5, 2004. The Q.931 dissector in Ethereal before 0.10.0, and Tethereal, allows remote attackers to cause a denial of service (crash) via a malformed Q.931, which triggers a null dereference.
When was CVE-2003-1013 disclosed?
CVE-2003-1013 was first published in the National Vulnerability Database on January 5, 2004, 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-1013 actively exploited?
CVE-2003-1013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2003-1013?
CVE-2003-1013 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2003-1013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-1013, 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-1013

Explore →

Is Your Infrastructure Affected by CVE-2003-1013?

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

Start Free Scan →Browse All CVEs