Bug 656437 (CVE-2010-4301) - CVE-2010-4301 Wireshark: Infinite loop in Zigbee ZCL dissector
Summary: CVE-2010-4301 Wireshark: Infinite loop in Zigbee ZCL dissector
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2010-4301
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-23 18:12 UTC by Jan Lieskovsky
Modified: 2021-03-26 15:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 09:32:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Lieskovsky 2010-11-23 18:12:37 UTC
A denial of service flaw was found in the way the Zigbee ZCL
dissector of Wireshark network traffic analyzer processed
certain captures. A remote attacker could use this flaw to
cause an infinite loop, if the local user opened 
a specially-crafted captures file in Wireshark.

References:
[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5303
[2] http://www.wireshark.org/security/wnpa-sec-2010-14.html
[3] http://www.openwall.com/lists/oss-security/2010/11/22/17

Comment 1 Jan Lieskovsky 2010-11-23 18:17:30 UTC
This issue did NOT affect the versions of the wireshark package,
as shipped with Red Hat Enterprise Linux 4, 5, or 6, as those
versions do not provide support for the Zigbee Cluster Library
(ZCL) protocol yet.

--

This issue did NOT affect the versions of the wireshark package,
as shipped with Fedora release of 12 and 13, as those versions
do not provide support for the Zigbee Cluster Library (ZCL)
protocol yet.

This issue does NOT affect the version of the wireshark package,
as shipped with Fedora release of 14 (relevant packages are already
updated to v1.4.2).

Comment 2 Jan Lieskovsky 2010-11-23 18:20:23 UTC
Statement:

This issue did not affect the versions of wireshark shipped with
Red Hat Enterprise Linux 4, 5, and 6, as they did not include
support for the Zigbee Cluster Library (ZCL) protocol.


Note You need to log in before you can comment on or make changes to this bug.