Wireshark-bugs: [Wireshark-bugs] [Bug 2144] New: crash on specific snmp packet
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 28 Dec 2007 13:28:25 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2144

           Summary: crash on specific snmp packet
           Product: Wireshark
           Version: 0.99.7
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ernst.vogel@xxxxxxxxxxxx


Build Information:
Version 0.99.7 (SVN Rev 23910)

Compiled with GTK+ 2.12.1, with GLib 2.14.3, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with SMI 0.4.5, with ADNS, with Lua 5.1,
with
GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio
V19-devel, with AirPcap.

Running on Windows Server 2003 Service Pack 2, build 3790, with WinPcap version
4.0.2 (packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804
--
With snmp-protocol enabled, wireshark 0.99.7 crashes with an specific
snmp-packet.Before the crash, the following printout was on the debug-console
window:

"Warn dissector bug, protocol snmp, in packet 3441: STATUS_ACCESS_VIOLATION:
dissector accessed an invalid memory address"

On Wireshark 0.99.6a the same packet was displayed without problems.
I have extracted this packet from the temporary capture-file (but I dont't know
how to attach it)?
With 0.99.7 it's not possible to load it (it will crash), with 0.99.6a it's ok.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.