Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9832] New: Copying Binary/Octal data from Content field in packet

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9832
Summary	Copying Binary/Octal data from Content field in packet
Classification	Unclassified
Product	Wireshark
Version	1.10.5
Hardware	x86-64
OS	Windows 8.1
Status	UNCONFIRMED
Severity	Trivial
Priority	Low
Component	Wireshark
Assignee	bugzilla-admin@wireshark.org
Reporter	nanderson7@gmail.com

Created attachment 12599 [details]
pre-crash image

Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)

Copyright 1998-2013 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 (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.

Running on 64-bit Windows 8, build 9200, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
       Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, with 3981MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

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

Check the man page and http://www.wireshark.org for more information.
--
I fired up the nitroba PCAP
(http://digitalcorpora.org/corp/nps/packets/2008-nitroba/nitroba.pcap),
searched the value 'amy789smith', and attempted to copy the Value of the Yahoo
YMSG Messenger Protocol (Authentication) Packet.  The specific field was
"Content: 1\300\200amy789smith\300\200"

Essentially it seems that copying binary/octal data to the clipboard is
breaking?  Opened it up in WinDBG and it appeared to be dereferencing two null
pointers.

---

      You are receiving this mail because:

• You are watching all bug changes.