Wireshark-bugs: [Wireshark-bugs] [Bug 9596] New: IEC60870-5-104 incorrect Integrated Totals pars
| Bug ID |
9596
|
| Summary |
IEC60870-5-104 incorrect Integrated Totals parsing
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.3
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
jaka.fritz@inea.si
|
Created attachment 12382 [details]
Interrogation and response
Build Information:
Version 1.10.3 (SVN Rev 53022 from /trunk-1.10)
Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Nov 1 2013), with AirPcap.
Running on 32-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz, with 3319MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
After performing Counter Interrogation command, the Response is sent. The first
response has 4 Integrated Totals (IT) with IOA addresses from 304 to 300. The
Wireshark displays and parses up to address of the first data point (IOA: 304).
The timestamps are also sent with data. The values of the IOA 300 is 0xAABB
CCDD and the value of IOA 301 is 0x00FF FFFF (to help debug :)).
Third packet is a spontaneous response of the IOA 301 redirected to IOA 29997.
I didn't bother looking at bug#5889 (IEC60870-5-104 protocol, incorrect
decoding of timestamp type CP56Time2a) - lazy me. I hope it's not a repost.
Cheers,
Jaka
You are receiving this mail because:
- You are watching all bug changes.
