| Bug ID |
11577
|
| Summary |
SNA Connection Setup Segment 0D incorrectly dissected as sna.control.key==0x0D
|
| Product |
Wireshark
|
| Version |
1.12.1
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13901 [details]
capture showing SNA frames carrying Connection Setup segments
Build Information:
wireshark 1.12.1 (Git Rev Unknown from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> 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.20.1, with Cairo 1.8.8, with Pango 1.28.1, with
GLib 2.26.1, with libpcap, with libz 1.2.3, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.7.0, with Lua 5.1, without Python,
with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT Kerberos, without GeoIP, without
PortAudio, with AirPcap.
Running on Linux 2.6.32-504.7.1.el6.x86_64, with locale en_US.utf8, with
libpcap
version 1.4.0, with libz 1.2.3, GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
Built using gcc 4.4.7 20120313 (Red Hat 4.4.7-4).
--
Under certain circumstances wireshark fails to dissect an SNA RTP Optional
Segment Type: Connection Setup Segment (0x0d).
It is mis-interpreted as a sna.control.key == 0x0d
Mode / Class-of-Service / Virtual-Route-Identifier List Control Vector instead
resulting in a Malformed Packet (Exception occurred)
The attached capture shows a successful dissection in frame 3 and 2 failing
ones in frame 1 and 2
You are receiving this mail because:
- You are watching all bug changes.