CVE-2023-0667

CRITICALNVD 6.59.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: MODERATE) published 2023-06-07. NVD baseline CVSS 6.5; sources differ by 3.3.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2023-12699 (ENISA EUVD) · GHSA-m7h5-4hfx-r2mh (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Due to failure in validating the length provided by an attacker-crafted MSMMS packet, Wireshark version 4.0.5 and prior, in an unusual configuration, is susceptible to a heap-based buffer overflow, and possibly code execution in the context of the process running Wireshark

CVSS v3
6.5
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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 available. Apply it within your standard update timelines.
EPSS PROB
2.0%
EPSS %ILE
80th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

June 7, 2023

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Patch available.
Web page

http://takeonme.org/cves/cve-2023-0667/

https://takeonme.org/cves/CVE-2023-0667.html
Web page

Wireshark: Multiple Vulnerabilities (GLSA 202309-02) — Gentoo security

https://security.gentoo.org/glsa/202309-02
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3906-1] wireshark security update

https://lists.debian.org/debian-lts-announce/2024/09/msg00049.html
Web page🟡 PoC Available

MSMMS parsing buffer overflow (#19086) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/issues/19086

Vendor Advisories for CVE-2023-0667(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark3.4.10-0+deb11u1 ... 3.4.9-1 (7 versions)
  • every version up to 3.4.16-0+deb11u1: fixed in 3.4.16-0+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.0.3-1, 4.0.5-1~exp1
  • every version up to 4.0.6-1~deb12u1: fixed in 4.0.6-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark—
  • every version up to 4.0.6-1: fixed in 4.0.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark—
  • every version up to 4.0.6-1: fixed in 4.0.6-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 82× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 246 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-0667?
CVE-2023-0667 is a critical-severity vulnerability; its CVE record was published on June 7, 2023. Due to failure in validating the length provided by an attacker-crafted MSMMS packet, Wireshark version 4.0.5 and prior, in an unusual configuration, is susceptible to a heap-based buffer overflow, and possibly code execution in the context of the process running Wireshark
When was CVE-2023-0667 made public?
CVE-2023-0667 was made public on May 22, 2023: that is the date its CVE record's CNA, Austin Hackers Anonymous, gives for when the vulnerability was made public. The CVE record itself was published on June 7, 2023. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2023-0667 actively exploited?
CVE-2023-0667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0667?
CVE-2023-0667 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2023-0667?
A fix for CVE-2023-0667 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0667 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-0667

Explore →

Is Your Infrastructure Affected by CVE-2023-0667?

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