Wireshark-bugs: [Wireshark-bugs] [Bug 10834] New: Dissector HPFEEDS fails in some cases

Date: Tue, 06 Jan 2015 20:38:29 +0000
Bug ID 10834
Summary Dissector HPFEEDS fails in some cases
Product Wireshark
Version Git
Hardware x86
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 13370 [details]
Capture with packets that create errors in the current hpfeeds dissector

Build Information:
TShark (Wireshark) 1.99.2 (v1.99.2rc0-473-gfc4e944 from unknown)

Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 libpcap, without POSIX capabilities, without libnl, with
libz 1.2.8, with GLib 2.40.2, without SMI, with c-ares 1.10.0, without Lua,
with
GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP.

Running on Linux 3.13.0-43-generic, with locale
LC_CTYPE=en_US.UTF-8;LC_NUMERIC=it_IT.UTF-8;LC_TIME=it_IT.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=it_IT.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=it_IT.UTF-8;LC_NAME=it_IT.UTF-8;LC_ADDRESS=it_IT.UTF-8;LC_TELEPHONE=it_IT.UTF-8;LC_MEASUREMENT=it_IT.UTF-8;LC_IDENTIFICATION=it_IT.UTF-8,
with libpcap version 1.5.3, with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt
1.5.3.
Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz (with SSE4.2)

Built using gcc 4.8.2.

--
The HPFEEDS dissector fails in some cases:

1) when a json payload is in the channel, but the channel is not
CH_GEOLOC_EVENTS (decoded as flat data)
2) then the channel is CH_GEOLOC_EVENTS, but the payload is not json (decoded
with wrong json)

Attached you can find a sample capture with 

- a packet for case (1)
- a standard packet (worked with previous version)
- a packet for case (2)

I'm submitting a patch for that that references this bug.


You are receiving this mail because:
  • You are watching all bug changes.