Skip to main content
CVE-2023-1993VulnerabilityPublished Updated

CVE-2023-1993: Excessive iteration in Wireshark

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.0.5 or 3.6.13 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
4.0% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.5, 3.6.13
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 12 Apr 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 debian/wireshark to 4.0.5 or 3.6.13.

Affected software

ProductAffectedFixed in
Debiandebian/wiresharkpkg:deb/debian/wiresharkOther threatsAffected
  • <4.0.5
  • <3.6.13
Fixed in
  • 4.0.5
  • 3.6.13

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 version 3.6.13 or 4.0.5 or later once official patches are released by the Wireshark Foundation. 2. If you cannot patch yet, avoid opening capture files from untrusted or unknown sources. 3. Limit the use of Wireshark to trusted network environments and restrict access to capture files. 4. Employ network segmentation and filtering to reduce exposure to malicious LISP packets, especially from external or untrusted networks. 5. Educate users and analysts about the risk of opening suspicious capture files and encourage verification of file sources. 6. Monitor Wireshark usage logs and system performance for signs of excessive resource consumption that may indicate exploitation attempts. 7. Consider using alternative network analysis tools temporarily if patching is delayed and risk is high.

Description

LISP dissector large loop in Wireshark 4.0.0 to 4.0.4 and 3.6.0 to 3.6.12 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…