Name: Kafka dissector memory exhaustion.
Date: December 7, 2022
Affected versions: 4.0.0 to 4.0.1, 3.6.0 to 3.6.9
Fixed versions: 4.0.2, 3.6.10
The Kafka dissector could consume excessive amounts of 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 4.0.2, 3.6.10 or later.