wnpa-sec-2016-42 · WSP infinite loop
Summary
Name: WSP infinite loop
Docid: wnpa-sec-2016-42
Date: July 27, 2016
Affected versions: 2.0.0 to 2.0.4, 1.12.0 to 1.12.12
Fixed versions: 2.0.5, 1.12.13
References:
Wireshark bug 12594
Details
Description
The WSP dissector could go into an infinite loop. Discovered by Chris Benedict, Aurelien Delaitre, NIST SAMATE Project.
Impact
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.
Resolution
Upgrade to Wireshark 2.0.5, 1.12.13 or later.
Go Beyond with Riverbed Technology
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