The MIH, MPEG DSM-CC, eDonkey, and MEGACO protocol dissectors could go into an infinite loop.

Impact

Discovered in our internal testing environment. We are unaware of any exploits for this issue. 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.

Resolution

Upgrade to Wireshark 4.6.7, 4.4.17 or later.