Name: RELOAD dissector infinite loop
Date: May 17, 2013
Affected versions: 1.8.0 to 1.8.6
Fixed versions: 1.8.7
The RELOAD dissector could go into an infinite loop. Discovered by Evan Jensen.
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.7 or later.