Name: WBXML infinite loop
Date: June 7, 2016
Affected versions: 1.12.0 to 1.12.11
Fixed versions: 1.12.12
The WBXML dissector could go into an infinite loop. Discovered by Chris Benedict, Aurelien Delaitre, NIST SAMATE Project.
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.12 or later.