Wireshark-bugs: [Wireshark-bugs] [Bug 6734] New: GOOSE Messages don't use the length field to pe
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 13 Jan 2012 12:02:08 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6734

           Summary: GOOSE Messages don't use the length field to perform
                    the dissection
           Product: Wireshark
           Version: 1.6.5
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: rapphil@xxxxxxxxx


Created attachment 7681
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7681
Example of goose message with pad bytes at the end.

Build Information:
Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)

Copyright 1998-2012 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 Jan
10 2012), 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.
--



Wireshark is using the length of the Ethernet packet instead of using the
length field of a goose message to dissect it.

If a goose Ethernet packet has pad bytes at the end, Wireshark will not be able
to dissect it properly.


As one can see, pad bytes are acceptable at the end of a goose message. (IEC
61850 8-2, pag 114, v 1.0, figure C.1).

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