Wireshark-bugs: [Wireshark-bugs] [Bug 6303] New: Incorrect dissection of ZigBee "Configure Repor
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 1 Sep 2011 12:47:07 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6303

           Summary: Incorrect dissection of ZigBee "Configure Reporting
                    Response" frame
           Product: Wireshark
           Version: 1.6.1
          Platform: All
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: diego@xxxxxxxxxxxxxxxx


Created an attachment (id=6909)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6909)
Screenshot of the request and its response dissections

Build Information:
Version 1.6.1 (SVN Rev 38096 from /trunk-1.6)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Jul
18 2011), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Dissection of the "Configure Reporting Response" packet is incorrect. See
attached images for an example including a request and its response.

The request is to configure a single attribute. The response contains only one
status record. WireShark is incorrectly showing four status records, one byte
each. This is incorrect, as the response contains a single status record, which
is four bytes long (1 byte status + 1 byte direction + 2 bytes attribute ID).
This is described in the ZCL specification, page 30
(075366r01ZB_AFG-ZigBee_Cluster_Library_Public_download_version.pdf).

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.