| Bug ID |
8306
|
| Summary |
BACnet - Loop Object - Setpoint-Reference property does not decode correctly
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.8.4
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
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_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.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 Feb 8 2013), 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.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM)2 Duo CPU P9700 @ 2.80GHz, with 3571MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 30319
--
When reading or writing the Loop Object Setpoint-Reference property, the
detailed decoding was incorrect. The attached pcap shows an example. The
attached patch fixes the problem. The changes have been fuzz tested.
You are receiving this mail because:
- You are watching all bug changes.