Name: Wireshark sFlow dissector infinite loop
Date: November 28, 2012
Affected versions: 1.8.0 to 1.8.3, 1.6.0 to 1.6.13.
Fixed versions: 1.8.4
The sFlow 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 1.8.4 or later.