Hide Forgot
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-4075 to the following vulnerability: epan/dissectors/packet-gmr1_bcch.c in the GMR-1 BCCH dissector in Wireshark 1.8.x before 1.8.8 does not properly initialize memory, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. References: [1] http://anonsvn.wireshark.org/viewvc/trunk/epan/dissectors/packet-gmr1_bcch.c?r1=44674&r2=44673&pathrev=44674 [2] http://anonsvn.wireshark.org/viewvc?view=revision&revision=44674 [3] http://www.wireshark.org/docs/relnotes/wireshark-1.8.8.html [4] http://www.wireshark.org/security/wnpa-sec-2013-33.html [5] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7664 [6] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8726
This issue did NOT affect the version of the wireshark package, as shipped with Fedora release of 17. -- This issue affects the version of the wireshark package, as shipped with Fedora release of 18.
Created wireshark tracking bugs for this issue Affects: fedora-18 [bug 972762]
The version of wireshark shipped with Red Hat Enterprise Linux 5 and 6 does not have support for GEO-Mobile Radio (1) BCCH protocol. Therefore this flaw does not affect these versions.
External References: http://www.wireshark.org/security/wnpa-sec-2013-33.html
wireshark-1.10.2-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
wireshark-1.10.2-7.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
wireshark-1.10.2-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I hope it is appropriate to re-open the bug due to the reproducer in the private comment #9.
Statement: Red Hat Product Security has rated this issue as having Low security impact for Red Hat Enterprise Linux 6. It does not affect the version of wireshark shipped with Red Hat Enterprise Linux 5. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
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