Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9578] New: Homeplug dissector bug: STATUS_ACCESS_VIOLATION: dissector accessed

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9578
Summary	Homeplug dissector bug: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
Classification	Unclassified
Product	Wireshark
Version	SVN
Hardware	x86-64
OS	Windows 7
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Dissection engine (libwireshark)
Assignee	bugzilla-admin@wireshark.org
Reporter	christopher.maynard@gtech.com

Build Information:
Version 1.11.3 (SVN Rev 54224 from /trunk)

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, 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  9 2013),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, 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-2540M CPU @ 2.60GHz, with 8072MB of physical
memory.

Built using Microsoft Visual C++ 10.0 build 30319

--
I encountered the following bug in the homeplug dissector:

11:11:50          Warn Dissector bug, protocol HomePlug, in packet 1:
STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address

To reproduce the bug, first enable the frame dissector's "Treat all frames as
DOCSIS frames" preference, then load the attached capture file.  You may need
to apply a display filter (I used frame.md5_hash) and then clear the filter.

This dissector uses the ptvcursor API, which I'm not all that familiar with. 
The exception appears to occur in the call to ptvcursor_add() within the
dissect_homeplug_unknown() function.

---

      You are receiving this mail because:

• You are watching all bug changes.