Crash copying data from captured packet

This issue was migrated from bug 6980 in our old bug tracker.

Original bug information:

Reporter: Carlo Di Dato
Status: RESOLVED DUPLICATE
Product: Wireshark
Component: GTK+ UI
OS: Windows 7
Platform: x86
Version: 1.6.5

Attachments:

test.pcap: PoC

Duplicate of issue #6089 (closed)

Carlo Di Dato said:

Build Information: Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)

Copyright 1998-2012 Gerald Combs <gerald@‍wireshark.org> 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 (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jan 10 2012), with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

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

Check the man page and http://www.wireshark.org for more information.

---

Steps to reproduce:

1. open the attached packet (test.pcap)
2. expand "Telnet" node
3. right click on "Data"
4. select copy "Description" and or "Value"

the program crash:

module: libgtk-win32-2.0-0.dll

6421D665   66:833C43 0A     CMP WORD PTR DS:[EBX+EAX*2],0A

Regards

added oswindows uigtk version1.6 labels

Jeff Morriss said:

(Did you mean to attach a sample capture?)

Carlo Di Dato said:

Created attachment 8067
PoC

Sorry, I was sure I already uploaded the attachment :)

Jeff Morriss said:

Thanks--I wanted to confirm that there's some non-ASCII stuff in there which is what causes the problem.

*** This bug has been marked as a duplicate of bug #6089 (closed) ***

closed

marked this issue as a duplicate of #6089 (closed)

marked this issue as related to #6089 (closed)