Name: FCP dissector crash
Date: February 23, 2018
Affected versions: 2.4.0 to 2.4.4, 2.2.0 to 2.2.12
Fixed versions: 2.4.5, 2.2.13
Wireshark bug 14374
The FCP dissector could crash. Discovered by Otto Airamo and Antti Levomäki, Forcepoint.
It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upgrade to Wireshark 2.4.5, 2.2.13 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