Cyber Resilience

CVE-2024-2955

Wireshark 4.0.0 – 4.0.14

Public PoC
Published
26 March 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.014 70th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2024-2955 is a high-severity Mismatched Memory Management Routines (CWE-762) vulnerability in Wireshark Wireshark. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

T.38 dissector crash in Wireshark 4.2.0 to 4.0.3 and 4.0.0 to 4.0.13 allows denial of service via packet injection or crafted capture file

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-4853Same product: Fedoraproject Fedora
CVE-2024-24479Same product: Fedoraproject Fedora
CVE-2024-4855Same product: Fedoraproject Fedora
CVE-2024-24476Same product: Fedoraproject Fedora
CVE-2024-4854Same product: Fedoraproject Fedora
CVE-2023-3648Same product: Wireshark Wireshark
CVE-2026-7378Same product: Wireshark Wireshark
CVE-2026-15165Same product: Wireshark Wireshark
CVE-2026-15167Same product: Wireshark Wireshark
CVE-2024-24478Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
4.0.0 — 4.0.14 · 4.2.0 — 4.2.4
fedoraproject
fedora
39, 40

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover mismatched memory calls through static analysis, dynamic testing, or fuzzing.

Documented development standards and tools can enforce or check for correct pairing of allocators and deallocators.

An SDLC that incorporates security can embed memory-safety requirements, reducing the chance such coding errors are introduced.

Engineering principles can mandate consistent use of matching allocation and deallocation routines during design and implementation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent mismatched alloc/free via code review and static analysis, but fixing this single CWE only partially fulfills the broad control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect mismatched alloc/free pairs before release.

prevents

Secure development lifecycle mandates consistent allocation/deallocation patterns that prevent mismatched memory routines.

prevents

Application security requirements can specify correct use of release functions and pointer validation.

degrades

Secure system architecture and engineering principles require use of matching allocators and deallocators.

prevents

Secure coding standards directly prohibit mismatched memory-management calls and enforce safe patterns.

References