CVE-2023-0416VulnerabilityPublished 24 Jan 2023Updated 3 Nov 2025

CVE-2023-0416: Expired Pointer Dereference in Wireshark

Affects WiresharkSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.0.3 or 3.6.11 when convenient.

Data as of 26 Oct 2026, 08:30 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 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.3, 3.6.11

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 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

Upgrade wireshark/wireshark to 4.0.3 or 3.6.11.

Affected software

Product	Affected	Fixed in
GitHubwireshark/wireshark`pkg:github/wireshark/wireshark`Other threats	Affected <3.6.11 <4.0.3	Fixed in 3.6.11 4.0.3

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.11, 4.0.3, or later as soon as these patches become available from the Wireshark Foundation. 2. If you cannot patch yet, restrict the opening of capture files to trusted sources only, and avoid analyzing untrusted or unknown capture files. 3. Implement network segmentation and filtering to limit exposure to malicious packets that could trigger the vulnerability, especially on networks where Wireshark is used. 4. Use sandboxing or containerization techniques to isolate Wireshark processes, minimizing the impact of crashes on host systems. 5. Educate security analysts and network engineers about the risk of opening untrusted capture files and encourage verification of file provenance. 6. Monitor Wireshark usage logs and system stability to detect potential exploitation attempts or crashes. 7. Employ alternative or additional network monitoring tools temporarily if patching is delayed, to maintain visibility. 8. Review and update incident response procedures to account for potential disruptions caused by this vulnerability.

Description

GNW dissector crash 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 of CVE-2023-0416 is the potential denial of service of Wireshark instances used in network monitoring, incident response, and forensic investigations. This can delay detection and response to network threats, increasing the risk of undetected attacks or prolonged outages. Confidentiality and integrity impacts are limited but present, as the crash could potentially be leveraged in complex attack chains. Organizations in sectors with high reliance on network analysis tools—such as telecommunications, finance, critical infrastructure, and government—may experience operational disruptions. The disruption could affect security teams’ ability to analyze traffic and respond to incidents promptly. Additionally, if Wireshark is used in automated monitoring pipelines, crashes could cause gaps in network visibility. Since Wireshark is widely used across Europe, the vulnerability poses a broad risk, especially where older versions remain in use due to operational constraints or delayed patching. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as crafted capture files can be distributed via email or file sharing. The vulnerability also poses a risk in environments where untrusted capture files are analyzed without sufficient sandboxing or isolation.

CWE-404Improper Resource Shutdown or Release (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not release or incorrectly releases a resource before it is made available for re-use.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error…
Implementation
Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
Attack patterns
TCP Fragmentation (opens in a new tab)
UDP Fragmentation (opens in a new tab)
ICMP Fragmentation (opens in a new tab)
BlueSmacking (opens in a new tab)
Flooding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-404

Technical details

References

Community reviews

Related threats