Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 13110] New: Dissector skips DICOM command

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	13110
Summary	Dissector skips DICOM command
Product	Wireshark
Version	2.2.1
Hardware	x86-64
OS	Windows 7
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Dissection engine (libwireshark)
Assignee	bugzilla-admin@wireshark.org
Reporter	b.schoppmeier@bas-consult.de

Created attachment 15049 [details]
Screen shot

Build Information:
Version 2.2.1 (v2.2.1-0-ga6fbd27 from master-2.2)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.6.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
German_Germany.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980),
based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15,
with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (with SSE4.2), with 8097MB of physical
memory.

--
In the course of sendig a DICOM print request two N-SET commands - among others
- are sent to the printer. The first N-SET command is displayed properly in
Wireshark (see attachment Fist N-SET.png). The second N-SET command, however,
ist missing from display (see attachment Second N-SET.png). It correctly
dissects the beginning of the PDU until byte # 0x41. Thereafter it displays the
accompanying data (see attachment Second N-SET_2.png) form byte # 0xc4 on. The
content from 0x42 to 0xc3 is not reflected by the DICOM dissector. Close
examination of the hex data reveals that is the N-SET command with SOP class
and SOP instance affected.

Complete session is in attachment Print.pcapng

---

      You are receiving this mail because:

• You are watching all bug changes.