Name: IAX2 infinite loop
Date: April 22, 2016
Affected versions: 2.0.0 to 2.0.2, 1.12.0 to 1.12.10
Fixed versions: 2.0.3, 1.12.11
The IAX2 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.0.3, 1.12.11 or later.