CVE-2020-15466
📋 TL;DR
This CVE describes an infinite loop vulnerability in Wireshark's GVCP dissector that can cause denial of service. When processing malicious network packets, Wireshark versions 3.2.0 through 3.2.4 could hang or crash. This affects anyone using vulnerable Wireshark versions to analyze network traffic.
💻 Affected Systems
- Wireshark
📦 What is this software?
Leap by Opensuse
Leap by Opensuse
Wireshark by Wireshark
⚠️ Risk & Real-World Impact
Worst Case
Complete denial of service where Wireshark crashes or becomes unresponsive, potentially causing data loss of captured packets and disrupting network analysis activities.
Likely Case
Wireshark becomes unresponsive when processing malicious GVCP packets, requiring restart and losing any unsaved capture data.
If Mitigated
Minimal impact if Wireshark is not used to analyze GVCP traffic or if proper network segmentation prevents malicious packets from reaching analysis systems.
🎯 Exploit Status
Exploitation requires sending specially crafted GVCP packets to a network interface being monitored by Wireshark. No authentication needed as this is a parsing vulnerability.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Wireshark 3.2.5 and later
Vendor Advisory: https://www.wireshark.org/security/wnpa-sec-2020-10.html
Restart Required: Yes
Instructions:
1. Download Wireshark 3.2.5 or later from wireshark.org. 2. Uninstall current version. 3. Install updated version. 4. Restart system to ensure all components are updated.
🔧 Temporary Workarounds
Disable GVCP Dissector
allTemporarily disable the vulnerable GVCP dissector to prevent exploitation while awaiting patch
wireshark -o gvcp.desegment:false
tshark -o gvcp.desegment:false
Filter GVCP Traffic
allUse capture filters to exclude GVCP traffic from being processed by Wireshark
wireshark -f "not port 3956"
tshark -f "not port 3956"
🧯 If You Can't Patch
- Restrict network access to Wireshark systems to prevent malicious GVCP packets from reaching them
- Use alternative network analysis tools temporarily until Wireshark can be updated
🔍 How to Verify
Check if Vulnerable:
Check Wireshark version: Help → About Wireshark on GUI or 'wireshark --version' on command line. If version is between 3.2.0 and 3.2.4 inclusive, system is vulnerable.
Check Version:
wireshark --version | head -1
Verify Fix Applied:
Verify Wireshark version is 3.2.5 or later using 'wireshark --version' command. Test by capturing GVCP traffic to ensure no crashes occur.
📡 Detection & Monitoring
Log Indicators:
- Wireshark crash logs
- Application event logs showing Wireshark termination
- System logs showing high CPU usage from Wireshark process
Network Indicators:
- Unusual GVCP traffic patterns
- Multiple GVCP packets with malformed structure
- Traffic to port 3956 (GVCP default) with abnormal patterns
SIEM Query:
source="wireshark.log" AND ("crash" OR "hang" OR "unresponsive") OR destination_port=3956 AND packet_size<50
🔗 References
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00026.html
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00038.html
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16029
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=11f40896b696e4e8c7f8b2ad96028404a83a51a4
- https://lists.debian.org/debian-lts-announce/2021/02/msg00008.html
- https://security.gentoo.org/glsa/202007-13
- https://www.wireshark.org/security/wnpa-sec-2020-09.html
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00026.html
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00038.html
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16029
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=11f40896b696e4e8c7f8b2ad96028404a83a51a4
- https://lists.debian.org/debian-lts-announce/2021/02/msg00008.html
- https://security.gentoo.org/glsa/202007-13
- https://www.wireshark.org/security/wnpa-sec-2020-09.html