Name: IAX2 infinite loop
Date: March 3, 2017
Affected versions: 2.2.0 to 2.2.4, 2.0.0 to 2.0.10
Fixed versions: 2.2.5, 2.0.11
Wireshark bug 13432
The IAX2 dissector could go into an infinite loop. Discovered by Otto Airamo and Antti Levomäki, Forcepoint.
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.5, 2.0.11 or later.