Name: Kafka dissector memory leak
Date: December 9, 2020
Affected versions: 3.4.0, 3.2.0 to 3.2.8
Fixed versions: 3.4.1, 3.2.9
The Kafka dissector could leak memory.
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 3.4.1, 3.2.9 or later.