It was reported that Wireshark's X11 dissector could leak memory. 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, 1.10.14. Upstream bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11088 External References: https://www.wireshark.org/security/wnpa-sec-2015-15.html
Fixed in Fedora via: FEDORA-2015-8174 -- wireshark-1.10.14-1.fc20 FEDORA-2015-8150 -- wireshark-1.12.5-1.fc21
Patch ----- https://code.wireshark.org/review/gitweb?p=wireshark.git;a=patch;h=f69930acda21301961c50421a73981854ef30068
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
Statement: (none)
Mitigation: This flaw can be mitigated in wireshark by disabling the X11 protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "X11" and disable in. When using "tshark", the text interface, create a file called "disabled_protos" in the preferences folder (normally .wireshark folder in the home directory of the user running wireshark) and add "X11" to it. This should disable the X11 protocol.
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:0631 https://rhn.redhat.com/errata/RHSA-2017-0631.html