wnpa-sec-2020-09 · GVCP dissector infinite loop
Name: GVCP dissector infinite loop
Date: July 1, 2020
Affected versions: 3.2.0 to 3.2.4
Fixed versions: 3.2.5
Wireshark bug 16029
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.
Go Beyond with Riverbed Technology
Riverbed is Wireshark's primary sponsor and provides our funding. They also make great products that fully integrate with Wireshark.
I have a lot of traffic...
ANSWER: SteelCentral™ AppResponse 11
- • Full stack analysis – from packets to pages
- • Rich performance metrics & pre-defined insights for fast problem identification/resolution
- • Modular, flexible solution for deeply-analyzing network & application performance