First published: Sun Jul 05 2020(Updated: )
In Wireshark 3.2.0 to 3.2.4, the GVCP dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-gvcp.c by ensuring that an offset increases in all situations.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Wireshark Wireshark | >=3.2.0<=3.2.4 | |
openSUSE Leap | =15.1 | |
openSUSE Leap | =15.2 | |
Debian Debian Linux | =9.0 | |
ubuntu/wireshark | <3.2.5-1 | 3.2.5-1 |
ubuntu/wireshark | <3.2.3-1ubuntu0.1~ | 3.2.3-1ubuntu0.1~ |
debian/wireshark | 2.6.20-0+deb10u4 2.6.20-0+deb10u8 3.4.10-0+deb11u1 4.0.11-1~deb12u1 4.2.2-1 4.2.2-1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-15466 is a vulnerability in Wireshark 3.2.0 to 3.2.4 that could cause the GVCP dissector to go into an infinite loop.
The GVCP dissector vulnerability in Wireshark could potentially lead to an infinite loop, which may cause denial of service or crash the application.
To fix the Wireshark GVCP dissector vulnerability, you need to update to version 3.2.5-1 or later on Ubuntu or version 2.6.20-0+deb10u4 or later on Debian.
You can find more information about CVE-2020-15466 on the official Wireshark bugzilla page, the code review page, and the Wireshark security advisory page.