Name: GVCP dissector infinite loop
Date: July 1, 2020
Affected versions: 3.2.0 to 3.2.4
Fixed versions: 3.2.5
The GVCP dissector could go into an infinite loop.
It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upgrade to Wireshark 3.2.5 or later.