CVE-2024-2955
Wireshark 4.0.0 – 4.0.14
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
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
- 🇪🇺 ENISA EUVD: EUVD-2024-27896
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
CVEs Like This One
Affected Assets
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.
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.
Security testing in development can detect mismatched alloc/free pairs before release.
Secure development lifecycle mandates consistent allocation/deallocation patterns that prevent mismatched memory routines.
Application security requirements can specify correct use of release functions and pointer validation.
Secure system architecture and engineering principles require use of matching allocators and deallocators.
Secure coding standards directly prohibit mismatched memory-management calls and enforce safe patterns.