It was reported that Wireshark's ZigBee dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. This flaw is fixed in the following Wireshark versions: 1.12.7. Upstream bug(s): https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11389 External References: https://www.wireshark.org/security/wnpa-sec-2015-24
Created wireshark tracking bugs for this issue: Affects: fedora-all [bug 1253364]
wireshark-1.12.7-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update wireshark'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-13945
wireshark-1.12.7-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update wireshark'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-13946
CVE was assigned: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-6244
wireshark-1.12.7-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Patch ----- https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=31571144be5f03f054a9c7e195b38c2f5792fe54 https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=43c2e5769a17f0945fdcdabe35204a13ca9bbc85 https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=655b0dc623e29da212be3e205314624fe3182562
Several functions needed to be backported in tvbuff.{h,c} to correctly compute captured remaining length in zigbee dissector. tvb_captured_length_remaining() now returns 0 instead of -1, if an exception occurs. This makes g_malloc() not to allocate (guint)(-1) and continue. Fixed in wireshark-1.10.14-7.el7.
wireshark-1.12.7-2.fc22 has been pushed to the Fedora 22 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 7 Via RHSA-2015:2393 https://rhn.redhat.com/errata/RHSA-2015-2393.html
Statement: This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue affects the verison of wireshark as shipped with Red Hat Enterprise Linux 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 6.
Mitigation: This flaw can be mitigated in wireshark by disabling the ZigBee protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "ZigBee" 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 "ZigBee" to it. This should disable the ZigBee protocol.