Cyber Resilience

CVE-2024-4853

Memory Safety in Wireshark 3.6.0 – 3.6.23

Public PoCMemory Safety
Published
14 May 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 3.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS Score 0.0042 35th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2024-4853 is a low-severity Mismatched Memory Management Routines (CWE-762) vulnerability in Wireshark Wireshark. Its CVSS base score is 3.6 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 35th percentile by exploit likelihood (below the median); 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

Memory handling issue in editcap could cause denial of service via 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.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
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-2023-0667Same product: Wireshark Wireshark
CVE-2024-8250Same product: Wireshark Wireshark
CVE-2025-5601Same product: Wireshark Wireshark
CVE-2023-23456Same product: Fedoraproject Fedora
CVE-2024-4761Same product: Fedoraproject Fedora
CVE-2024-29133Same product: Fedoraproject Fedora
CVE-2021-21220Same product: Fedoraproject Fedora
CVE-2024-0517Same product: Fedoraproject Fedora
CVE-2023-2858Same product: Wireshark Wireshark
CVE-2023-2855Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
3.6.0 — 3.6.23 · 4.0.0 — 4.0.15 · 4.2.0 — 4.2.5
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.

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

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

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.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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 bounds-checking and safe memory handling.

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.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References