Skip to main content
CVE-2023-1161VulnerabilityPublished Updated

CVE-2023-1161: Wireshark · classic buffer overflow

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.0.4 or 3.6.12 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.4, 3.6.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Mar 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade wireshark/wireshark to 4.0.4 or 3.6.12.

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • <3.6.12
  • <4.0.4
Fixed in
  • 3.6.12
  • 4.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Wireshark to versions later than 3.6.11 or 4.0.3 where this vulnerability is patched. 2. Avoid opening capture files from untrusted or unknown sources to reduce risk of triggering the overflow. 3. Implement strict network segmentation and filtering to limit exposure to malicious ISO 15765 and ISO 10681 protocol traffic, especially from external or untrusted networks. 4. Use sandboxing or isolated environments for analyzing suspicious capture files to contain potential crashes. 5. Monitor Wireshark application logs and system stability to detect abnormal crashes that may indicate exploitation attempts. 6. Educate network analysts and incident responders about the risk and safe handling of capture files. 7. Employ endpoint protection solutions that can detect anomalous behavior or crashes in Wireshark processes. 8. Regularly review and update incident response procedures to handle potential denial of service scenarios affecting network analysis tools.

Description

ISO 15765 and ISO 10681 dissector crash in Wireshark 4.0.0 to 4.0.3 and 3.6.0 to 3.6.11 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…