Wireshark-bugs: [Wireshark-bugs] [Bug 11913] New: Dissector bug, protocol RPC: ...\epan\reassemb
| Bug ID |
11913
|
| Summary |
Dissector bug, protocol RPC: ...\epan\reassemble.c:1223: failed assertion "tvb_bytes_exist(...
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
paul.offord@advance7.com
|
Created attachment 14167 [details]
Stack dump
Build Information:
Version 2.1.0-Syncro (v2.1.0rc0-1137-gdca8f09 from master)
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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 Qt 5.5.1, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, with
AirPcap 4.1.0 build 1622.
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (with SSE4.2), with 8082MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
Wireshark throws an exception when dissecting and RPC v2 packet. The error
shown in the Packet Decode is:
[Dissector bug, protocol RPC: C:\Development\Wireshark\epan\reassemble.c:1223:
failed assertion "tvb_bytes_exist(tvb, offset, frag_data_len)"]
I am running a debug build of Wireshark, although I get the same problem with
the MSI download package for Wireshark v.2.0.
See frame 20 of the attached pcap file. I've also attached a stackdump taken
at the time of the problem.
This bug is similar to Bug 11198
You are receiving this mail because:
- You are watching all bug changes.
