VulnerabilityPublished 24 Jan 2023Updated 3 Nov 2025

CVE-2023-0411: Excessive Iteration in Wireshark

Affects WiresharkSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jan 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubwireshark/wireshark`pkg:github/wireshark/wireshark`Other threats	Affected >=3.6.0 <=3.6.10 >=4.0.0 <=4.0.2	Fixed in–

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

AI-suggested

Upgrade Wireshark to version 3.6.11 or 4.0.3 or later, where the vulnerability has been addressed.
Avoid opening capture files from untrusted or unknown sources to reduce risk of triggering excessive iteration loops.
Implement strict network segmentation and filtering to limit exposure to malicious packets that could exploit the vulnerability during live capture.
Educate security analysts and network engineers about the risks of opening suspicious capture files and encourage verification of file origins.
Use alternative or additional network analysis tools with robust input validation as a temporary measure until patches are applied.
Monitor network traffic for anomalies that could indicate attempts to exploit this vulnerability, such as unusual packet patterns or repeated crashes of Wireshark instances.
Employ endpoint protection solutions that can detect and block malicious capture files or suspicious network traffic patterns targeting Wireshark.

Description

Excessive loops in multiple dissectors in Wireshark 4.0.0 to 4.0.2 and 3.6.0 to 3.6.10 and allows denial of service via packet injection or crafted capture file

Impact

For European organizations, the primary impact is denial of service on systems running vulnerable Wireshark versions. This can disrupt network monitoring, incident response, and forensic investigations, potentially delaying detection and mitigation of other security incidents. Organizations relying heavily on Wireshark for operational security may experience reduced visibility into network traffic during an attack exploiting this vulnerability. While the confidentiality and integrity impacts are limited, availability degradation can affect security teams’ ability to respond promptly. Critical infrastructure operators, financial institutions, and large enterprises with dedicated security operations centers (SOCs) are particularly vulnerable to operational disruptions. Additionally, crafted capture files could be distributed via email or shared drives, increasing the risk of accidental exposure. The lack of known exploits reduces immediate risk, but the medium severity score and ease of triggering via user interaction warrant proactive mitigation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 00:05 UTC

WeaknessesCWE-834

Technical details

References

Community reviews

Related threats