Wireshark-bugs: [Wireshark-bugs] [Bug 5889] New: IEC60870-5-104 protocol, incorrect decoding of
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 3 May 2011 23:44:23 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5889

           Summary: IEC60870-5-104 protocol, incorrect decoding of
                    timestamp type CP56Time2a.
           Product: Wireshark
           Version: 1.4.6
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: wwwsss@xxxxxxxxxxxxxx


Created an attachment (id=6281)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6281)
Screenshot of incorrectly decoded timestamp

Build Information:
wireshark 1.4.6 (SVN Rev 36706 from /trunk-1.4)

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 (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI

0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with

Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Apr

18 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, 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 incorrectly decodes the milliseconds part of CP56Time2a timestamps.
The milliseconds are located in the
first 2 bytes of the timestamp (least significant byte first), and is a number
in the range [0..59999], for example the number 12345 would represent 12.345
seconds.

The attached screenshot shows an example: The packet bytes 68 92 should be
combined
to form 0x9268 = 37480 decimal, representing 37.480 seconds. However, Wireshark 
shows this as 37.224 seconds.

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