Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3751] New: [SNMP] Wireshark fails to initialize if a bad M

Date: Fri, 17 Jul 2009 08:04:30 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3751

           Summary: [SNMP] Wireshark fails to initialize if a bad MIB file
                    is loaded
           Product: Wireshark
           Version: 1.3.x (Experimental)
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: rjgodoy@xxxxxxxxxxxxxxx


Build Information:
Version 1.3.0-SVN-29128 (SVN Rev 29128)

Compiled with GTK+ 2.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, without Python, with GnuTLS 2.8.1, with Gcrypt
1.4.4, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 16
2009), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta4
(packet.dll version 4.1.0.1237), based on libpcap version 1.0 - branch, GnuTLS
2.8.1, Gcrypt 1.4.4, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--


In the attached testcase, Wireshark fails to initialize because a module
description is missing in the MIB file (yes, this is an extreme case, but
errors in a MIB should not affect the whole application). 

If the offending file is removed, Wireshark will complain of not finding the
MIB file, but it will not crash. I think the same behavior (reporting and
ignoring file) could be appliend when a severe parsing error occurs.

Procedure for replicating the bug:
1. Include BUG-MIB
2. Restart Wireshark.


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