Name: ASTERIX infinite loop
Date: January 23, 2017
Affected versions: 2.2.0 to 2.2.3, 2.0.0 to 2.0.9
Fixed versions: 2.2.4, 2.0.10
The ASTERIX dissector could go into an infinite loop. Discovered by Antti Levomäki and Christian Jalio, 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.4, 2.0.10 or later.