It was reported that Wireshark's WebSocket dissector could recurse excessively. 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. This flaw is fixed in versions the following Wireshark versions: 1.12.5. Upstream bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10989 External References: https://www.wireshark.org/security/wnpa-sec-2015-13.html
Fixed in Fedora via: FEDORA-2015-8150 -- wireshark-1.12.5-1.fc21
Upstream Fix ------------ https://code.wireshark.org/review/gitweb?p=wireshark.git;a=patch;h=4ee6bcbd2e03a25f1e6b0239558d9edeaf8040c0
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:2393 https://rhn.redhat.com/errata/RHSA-2015-2393.html