Name: Rbm dissector infinite loop
Date: April 8, 2019
Affected versions: 3.0.0
Fixed versions: 3.0.1
Wireshark bug 15612
The Rbm dissector could go into an infinite loop. Discovered by Mateusz Jurczyk.
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.0.1 or later.
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