Skip to main content
VulnerabilityPublished Updated

CVE-2023-4511: Wireshark · Infinite Loop

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.0.8 or 3.6.16 when convenient.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Aug 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 26 Oct 2026.

What to do

Upgrade wireshark/wireshark to 4.0.8 or 3.6.16.

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • <4.0.8
  • <3.6.16
Fixed in
  • 4.0.8
  • 3.6.16

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

AI-suggested

1. 2. If you cannot patch yet, avoid opening capture files from untrusted or unknown sources, especially those containing Bluetooth traffic. 3. Implement strict file validation and sandboxing when analyzing capture files to limit the impact of potential DoS conditions. 4. Educate SOC and network analysis personnel about the risks of processing unverified capture files and the symptoms of this DoS vulnerability. 5. Use network segmentation and access controls to limit exposure to crafted Bluetooth SDP packets from untrusted devices or networks. 6. Consider alternative tools or versions not affected by this vulnerability for critical analysis tasks if patching is delayed. 7. Employ automated scanning of capture files for anomalous Bluetooth SDP content before analysis. 8. Maintain incident response plans that include recovery procedures for Wireshark service disruptions. These targeted measures go beyond generic advice by focusing on operational controls and user awareness specific to this vulnerability’s exploitation vector.

Description

BT SDP dissector infinite loop in Wireshark 4.0.0 to 4.0.7 and 3.6.0 to 3.6.15 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…