The Microsoft Network Monitor file parser could go into a large loop. Discovered by Mayank Jangid (OpenSec Intelligence). 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.