Name: Wireshark MongoDB large loop
Date: August 15, 2012
Versions affected: 1.8.0 to 1.8.1
Fixed in: 1.8.2
The MongoDB dissector could go into a large loop. Reported by Ben Schmidt.
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 1.8.2 or later.