Name: CQL infinite loop
Date: April 3, 2018
Affected versions: 2.4.0 to 2.4.5
Fixed versions: 2.4.6
Wireshark issue 14530
The CQL dissector could to 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.4.6 or later.