Name: TN5250 infinite loops
Date: November 12, 2014
Affected versions: 1.12.0 to 1.12.1, 1.10.0 to 1.10.10
Fixed versions: 1.12.2, 1.10.11
The TN5250 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.2, 1.10.11 or later.