Wireshark-bugs: [Wireshark-bugs] [Bug 5897] New: Wireshark crashes with SIGABRT when handling "W

Date: Fri, 6 May 2011 01:03:23 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5897

           Summary: Wireshark crashes with SIGABRT when handling
                    "Wireshark pcapng (experimental)" format
           Product: Wireshark
           Version: 1.4.6
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: huzaifas@xxxxxxxxxx


Created an attachment (id=6294)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6294)
trace when opening file

Build Information:
wireshark 1.4.6

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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+ 2.22.0, with GLib 2.26.0, with libpcap 1.1.1,
without libz, without POSIX capabilities, without libpcre, with SMI 0.4.8,
without c-ares, without ADNS, with Lua 5.1, without Python, with GnuTLS 2.8.6,
with Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel
(built Jul 28 2009), without AirPcap.

Running on Linux 2.6.35.12-88.fc14.x86_64, with libpcap version 1.1.1, GnuTLS
2.8.6, Gcrypt 1.4.5.

Built using gcc 4.5.1 20100924 (Red Hat 4.5.1-4).

--
I found that wireshark-gnome crashes when saving a trace in the above format
and also when i try to open the file of above format (in wireshark-gnome)

I am attaching the trace for both the conditions. Sadly i cannot attach the
pcap-ng file since it contains network information.

Dies with SIGABRT, so it does not appear to have any security implication.

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