CVE-2024-24476
📋 TL;DR
This CVE describes a disputed buffer overflow vulnerability in Wireshark's address resolution and manufacturer lookup components that could allow remote attackers to cause denial of service. The vendor disputes this vulnerability, stating no releases were affected. Users running potentially vulnerable Wireshark versions for packet analysis could be impacted.
💻 Affected Systems
- Wireshark
📦 What is this software?
Fedora by Fedoraproject
Wireshark by Wireshark
⚠️ Risk & Real-World Impact
Worst Case
Remote attacker causes Wireshark to crash via specially crafted network traffic, potentially disrupting network analysis operations.
Likely Case
Denial of service causing Wireshark to crash when processing malicious packets.
If Mitigated
No impact if using unaffected versions or if traffic filtering prevents malicious packets from reaching Wireshark.
🎯 Exploit Status
Proof of concept available in references; exploitation requires ability to send network traffic to vulnerable system.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 4.2.0 (though vendor disputes vulnerability)
Vendor Advisory: https://gitlab.com/wireshark/wireshark/-/issues/19344
Restart Required: No
Instructions:
1. Update Wireshark to version 4.2.0 or later. 2. On Linux: Use package manager (apt/yum). 3. On Windows: Download from wireshark.org. 4. Verify version with wireshark --version.
🔧 Temporary Workarounds
Disable affected dissectors
allDisable manufacturer lookup and address resolution features
Edit preferences: Analyze → Enabled Protocols → Disable unnecessary protocols
Set 'Enable MAC name resolution' to false in preferences
Network segmentation
allIsolate Wireshark systems from untrusted networks
🧯 If You Can't Patch
- Restrict Wireshark usage to trusted network segments only
- Implement network monitoring to detect anomalous traffic patterns
🔍 How to Verify
Check if Vulnerable:
Check Wireshark version: wireshark --version | grep 'Wireshark'
Check Version:
wireshark --version
Verify Fix Applied:
Confirm version is 4.2.0 or later: wireshark --version
📡 Detection & Monitoring
Log Indicators:
- Wireshark crash logs
- Segmentation fault errors in system logs
Network Indicators:
- Unusual packet patterns targeting Wireshark ports
- Malformed packets in network captures
SIEM Query:
source="wireshark.log" AND ("segmentation fault" OR "crash" OR "buffer overflow")
🔗 References
- https://gist.github.com/1047524396/369ba0ccffe255cf8142208b6142be2b
- https://github.com/wireshark/wireshark/commit/108217f4bb1afb8b25fc705c2722b3e328b1ad78
- https://gitlab.com/wireshark/wireshark/-/issues/19344
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZT2BX7UARZVVWKITSZMHW7BHXGIKRSR2/
- https://gist.github.com/1047524396/369ba0ccffe255cf8142208b6142be2b
- https://github.com/wireshark/wireshark/commit/108217f4bb1afb8b25fc705c2722b3e328b1ad78
- https://gitlab.com/wireshark/wireshark/-/issues/19344
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZT2BX7UARZVVWKITSZMHW7BHXGIKRSR2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZT2BX7UARZVVWKITSZMHW7BHXGIKRSR2/