Wireshark-bugs: [Wireshark-bugs] [Bug 12975] New: Port scan causes Wireshark crash due to C++ ru
Date: Mon, 03 Oct 2016 14:23:59 +0000
Bug ID 12975
Summary Port scan causes Wireshark crash due to C++ runtime error
Product Wireshark
Version 2.2.0
Hardware x86-64
OS Windows Server 2012 R2
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter oodayoda@gmail.com

Created attachment 14971 [details]
Screen at time of failure

Build Information:
Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)

Copyright 1998-2016 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.3.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows Server 2012, build 9200, with locale English_United
States.1252, 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, without AirPcap.
       Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (with SSE4.2), with 8191MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Using Tripwire IP360 to perform a vulnerability scan and Wireshark doesn't
survive even the initial port scan. I'll attach a screen shot that gives some
hints as to what was going on at the time of the failure.

The IP360 has not caused such crashes on any of the earlier versions of
Wireshark that I have tried.


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