Name: HIP infinite loop
Date: September 16, 2014
Affected versions: 1.12.0
Fixed versions: 1.12.1
The HIP 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.12.1 or later.