Name: HTTP dissector crash
Date: June 7, 2013
Affected versions: 1.8.0 to 1.8.7, 1.6.0 to 1.6.15
Fixed versions: 1.8.8, 1.6.16
The HTTP dissector could overrun the stack.
It may be possible to make Wireshark consume excessive CPU resources and crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upgrade to Wireshark 1.8.8, 1.6.16 or later.