https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3536
Summary: Wireshark crashes when range_string is the data type
Product: Wireshark
Version: 1.0.8
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: Critical
Priority: High
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: preeti.syal@xxxxxxxxxxx
Build Information:
Copyright 1998-2008 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 with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, 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 V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, 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++ 8.0 build 50727
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Wireshark crashes in the following scenarios:
Crash 1:
Steps to reproduce->
>>Launch Wireshark
>>Click on the tab "Expression"
>>Select any parameter which is a range_string
>>Wireshark Crashes
Crash 2:
Steps to reproduce->
>>Launch Wireshark
>>In the "Filter:" box, enter any valid filter string containing range_string as the data type for eg:
protocol.param_name = 1.
Here, param_name is a range_string.
>> Try to edit the value on RHS to 0x001
>> Wireshark crashes
Suggestions:
For crash 1, edit dfilter_expr_dlg.c to introduce a function
build_range_enum_values and invoke it at places where build_enum_values is
invoked based upon the check:
"if (hfinfo->display & BASE_RANGE_STRING)"
Crash 2 is still under analysis.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.