Wireshark-bugs: [Wireshark-bugs] [Bug 11322] New: Regression: TCP reassembly can fail DISSECTOR_

Date: Tue, 30 Jun 2015 16:28:53 +0000
Bug ID 11322
Summary Regression: TCP reassembly can fail DISSECTOR_ASSERT
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 13697 [details]
Lua script hitting the problem

Build Information:
Wireshark 1.99.8 (Git Rev Unknown 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 GTK+ 3.10.8, with Cairo 1.13.1, with Pango 1.36.3, with
libpcap, with POSIX capabilities (Linux), without libnl, with libz 1.2.8, with
GLib 2.40.2, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, with GnuTLS
2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Feb 25 2014 21:09:53), without AirPcap.

Running on Linux 3.13.0-55-generic, with locale en_US.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-4980HQ CPU @ 2.80GHz

Built using gcc 4.8.4.
--
This may be only specific to Lua plugins, but I doubt it...

The behavior of TCP reassembly handling has changed somehow between 1.12.6 and
1.99.8 - the attached Lua script worked fine with the attached capture file in
1.12.6, but in 1.99.8 it hits a DISSECTOR_ASSERT for packet #6 and #12.  It
gets the following output:

16:26:00          Warn Dissector bug, protocol TCP, in packet 6:
/wireshark/epan/dissectors/packet-tcp.c:4163: failed assertion
"save_desegment_offset == pinfo->desegment_offset && save_desegment_len ==
pinfo->desegment_len"

I haven't investigated this issue yet - it may only be a Lua-specific issue,
but I doubt it because the Lua API C-code this script uses/invokes hasn't
changed between 1.12.6 and 1.99.8.


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