Name: SLSK dissector long loop
Date: April 12, 2017
Affected versions: 2.2.0 to 2.2.5, 2.0.0 to 2.0.11
Fixed versions: 2.2.6, 2.0.12
Wireshark issue 13576
The SLSK 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 2.2.6, 2.0.12 or later.