CVE-2012-5238

LOWCVSS v2 · 3.33.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 3.3 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:A/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 0.9% 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
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS v2: 3.3Exploit: None knownExposed: 0

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

epan/dissectors/packet-ppp.c in the PPP dissector in Wireshark 1.8.x before 1.8.3 uses incorrect OUI data structures during the decoding of (1) PPP and (2) LCP data, which allows remote attackers to cause a denial of service (assertion failure and application exit) via a malformed packet.

CVSS v2.0 (legacy)
3.3LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
3.3(low)
EG Risk
20(Track)
EG Risk 20/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
Severity33% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

October 4, 2012

Last Modified

April 29, 2026

References (24)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wireshark—1.8.2-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wireshark—1.8.2-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wireshark—1.8.2-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wireshark—1.8.2-2—

Data Freshness Timeline

(refreshed 6× in last 7d / 21× 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.

Showing the most recent 100 of 125 total refreshes for this CVE.

  1. 2026-08-27 14:20 UTCEPSS rescore
  2. 2026-08-26 14:40 UTCEPSS rescore
  3. 2026-08-25 13:43 UTCEPSS rescore
  4. 2026-08-24 07:23 UTCEPSS rescore
  5. 2026-08-24 02:52 UTCOSV refresh
  6. 2026-08-21 23:44 UTCEPSS rescore
  7. 2026-08-20 22:50 UTCEPSS rescore
  8. 2026-08-19 16:59 UTCEPSS rescore
  9. 2026-08-18 13:42 UTCEPSS rescore
  10. 2026-08-16 02:09 UTCEPSS rescore
  11. 2026-08-15 01:25 UTCEPSS rescore
  12. 2026-08-12 13:45 UTCEPSS rescore
  13. 2026-08-09 13:42 UTCEPSS rescore
  14. 2026-08-08 16:31 UTCEPSS rescore
  15. 2026-08-07 23:56 UTCOSV refresh
  16. 2026-08-07 16:21 UTCEPSS rescore
  17. 2026-08-06 13:42 UTCEPSS rescore
  18. 2026-08-05 19:12 UTCEPSS rescore
  19. 2026-08-04 15:04 UTCEPSS rescore
  20. 2026-08-02 02:22 UTCEPSS rescore
  21. 2026-07-30 01:26 UTCEPSS rescore
  22. 2026-07-28 15:31 UTCEPSS rescore
  23. 2026-07-26 13:46 UTCEG score recompute▲ 3.30
  24. 2026-07-25 14:12 UTCEPSS rescore
  25. 2026-07-23 14:14 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 01:08 UTCEG score recompute
  2. 2026-07-23 00:11 UTCEG score recompute
  3. 2026-07-22 21:50 UTCEG score recompute
  4. 2026-07-22 16:50 UTCOSV refresh
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-20 17:03 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-19 14:27 UTCEPSS rescore
  11. 2026-07-19 14:27 UTCEPSS rescore
  12. 2026-07-19 02:25 UTCEPSS rescore
  13. 2026-07-19 02:25 UTCEPSS rescore
  14. 2026-07-18 10:00 UTCEPSS rescore
  15. 2026-07-16 16:58 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-15 01:56 UTCEPSS rescore
  19. 2026-07-13 22:26 UTCEPSS rescore
  20. 2026-07-13 06:08 UTCEPSS rescore
  21. 2026-07-11 08:23 UTCEPSS rescore
  22. 2026-07-09 19:05 UTCEPSS rescore
  23. 2026-07-08 15:10 UTCEPSS rescore
  24. 2026-07-06 02:19 UTCEPSS rescore
  25. 2026-07-06 02:19 UTCEPSS rescore
  26. 2026-07-05 11:59 UTCOSV refresh
  27. 2026-07-05 02:26 UTCEPSS rescore
  28. 2026-07-04 06:27 UTCEPSS rescore
  29. 2026-07-01 15:02 UTCEPSS rescore
  30. 2026-06-30 23:19 UTCEPSS rescore
  31. 2026-06-30 23:19 UTCEPSS rescore
  32. 2026-06-29 14:02 UTCEPSS rescore
  33. 2026-06-28 04:53 UTCEPSS rescore
  34. 2026-06-28 04:53 UTCEPSS rescore
  35. 2026-06-27 03:05 UTCEPSS rescore
  36. 2026-06-25 13:46 UTCEPSS rescore
  37. 2026-06-24 14:02 UTCEPSS rescore
  38. 2026-06-24 14:02 UTCEPSS rescore
  39. 2026-06-23 21:30 UTCEPSS rescore
  40. 2026-06-22 14:22 UTCEPSS rescore
  41. 2026-06-22 14:22 UTCEPSS rescore
  42. 2026-06-21 14:53 UTCEPSS rescore
  43. 2026-06-21 01:57 UTCEPSS rescore
  44. 2026-06-21 01:56 UTCEPSS rescore
  45. 2026-06-19 19:23 UTCEPSS rescore
  46. 2026-06-19 19:22 UTCEPSS rescore
  47. 2026-06-18 17:49 UTCEPSS rescore
  48. 2026-06-18 17:49 UTCEPSS rescore
  49. 2026-06-17 17:49 UTCEPSS rescore
  50. 2026-06-17 17:49 UTCEPSS rescore
  51. 2026-06-16 23:14 UTCOSV refresh
  52. 2026-06-16 17:49 UTCEPSS rescore
  53. 2026-06-16 17:49 UTCEPSS rescore
  54. 2026-06-15 17:44 UTCEPSS rescore
  55. 2026-06-14 23:14 UTCEPSS rescore
  56. 2026-06-13 22:57 UTCEPSS rescore
  57. 2026-06-12 23:08 UTCEPSS rescore
  58. 2026-06-11 13:56 UTCEPSS rescore
  59. 2026-06-10 13:18 UTCEPSS rescore
  60. 2026-06-08 14:14 UTCEPSS rescore
  61. 2026-06-07 15:22 UTCEPSS rescore
  62. 2026-06-06 13:45 UTCEPSS rescore
  63. 2026-06-06 13:45 UTCEPSS rescore
  64. 2026-06-05 22:44 UTCEPSS rescore
  65. 2026-06-05 22:44 UTCEPSS rescore
  66. 2026-06-05 06:08 UTCEPSS rescore
  67. 2026-06-05 06:08 UTCEPSS rescore
  68. 2026-06-02 20:10 UTCEPSS rescore
  69. 2026-06-02 20:10 UTCEPSS rescore
  70. 2026-06-01 13:49 UTCEPSS rescore
  71. 2026-06-01 13:49 UTCEPSS rescore
  72. 2026-05-31 22:28 UTCEPSS rescore
  73. 2026-05-31 22:28 UTCEPSS rescore
  74. 2026-05-31 00:14 UTCEPSS rescore
  75. 2026-05-31 00:14 UTCEPSS rescore

Frequently asked(4)

What is CVE-2012-5238?
CVE-2012-5238 is a low vulnerability published on October 4, 2012. epan/dissectors/packet-ppp.c in the PPP dissector in Wireshark 1.8.x before 1.8.3 uses incorrect OUI data structures during the decoding of (1) PPP and (2) LCP data, which allows remote attackers to cause a denial of service (assertion failure and application exit) via a malformed packet.
When was CVE-2012-5238 disclosed?
CVE-2012-5238 was first published in the National Vulnerability Database on October 4, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-5238 actively exploited?
CVE-2012-5238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.6% of all scored CVEs.
How do I remediate CVE-2012-5238?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-5238, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-5238

Explore →

Is Your Infrastructure Affected by CVE-2012-5238?

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

Start Free Scan →Browse All CVEs