CVE-2024-2955: Mismatched Memory Management Routines in Wireshark
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
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/wiresharkto a version that resolves this vulnerability.Fixed in 4.0.17-0+deb12u1 - Upgrade
Upgrade
debian/wiresharkto a version that resolves this vulnerability.Fixed in 4.2.4-1 - Upgrade
Upgrade
debian/wiresharkto a version that resolves this vulnerability.Fixed in 4.0.17-0+deb12u3Fixed in 4.4.18-0+deb13u1Fixed in 4.4.19-0+deb13u1Fixed in 4.6.9-1 - Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 4.0.14-r0 - Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 4.2.4-r0 - Upgrade
Upgrade
Wiresharkto a version that resolves this vulnerability.Fixed in 4.2.4
Event History
Frequently Asked Questions
What is the severity of CVE-2024-2955?
CVE-2024-2955 is classified as a denial of service vulnerability that could crash the T.38 dissector in specific versions of Wireshark.
Which versions of Wireshark are affected by CVE-2024-2955?
CVE-2024-2955 affects Wireshark versions from 4.0.0 to 4.0.13 and versions from 4.2.0 to 4.0.3.
How do I fix CVE-2024-2955?
To fix CVE-2024-2955, update to the latest version of Wireshark that is not affected by this vulnerability.
What could exploit CVE-2024-2955?
CVE-2024-2955 can be exploited through packet injection or a crafted capture file.
What are the potential impacts of CVE-2024-2955?
The potential impact of CVE-2024-2955 includes crashing the Wireshark application, leading to a denial of service.