The TTL file parser could go into an infinite loop.

Impact

Discovered independently by Aisle Research (Dmitrijs Trizna, Luigino Camastra, Ze Sheng (O2Lab & TAMU), Igor Morgenstern) and Daniel Birtwhistle. We are unaware of any exploits for this issue. It may be possible to make Wireshark consume excessive CPU resources by convincing someone to read a malformed packet trace file.

Resolution

Upgrade to Wireshark 4.6.9 or later.