An infinite loop issue was discovered in Wireshark's MEGACO dissector. It may be possible to make Wireshark consume an excessive amount of CPU by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. This is reported to affect Wireshark versions 1.12.0, and 1.10.0 to 1.10.9. It is fixed in versions 1.12.1 and 1.10.10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10333 The version of Wireshark in Red Hat Enterprise Linux 5 and 6 is older than 1.10.x, and should not be affected. The version of Wireshark in Red Hat Enterprise Linux 7 is affected. External References: https://www.wireshark.org/security/wnpa-sec-2014-13.html
Created wireshark tracking bugs for this issue: Affects: fedora-all [bug 1142613]
wireshark-1.10.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
upstream fix ------------ https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=9112a099d7cc2cd924b7c667bf27f6e112b970c6
wireshark-1.12.1-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2014:1677 https://rhn.redhat.com/errata/RHSA-2014-1677.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 Via RHSA-2014:1676 https://rhn.redhat.com/errata/RHSA-2014-1676.html