| Bug ID |
11152
|
| Summary |
Wireshark decodes some valid RTP packets as STUN packets.
|
| Product |
Wireshark
|
| Version |
1.12.4
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13576 [details]
capture that shows two RTP packets as STUN packets
Build Information:
Version 1.12.4 (v1.12.4-0-gb4861da from master-1.12)
Copyright 1998-2015 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.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 4 2015),
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 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Xeon(R) CPU W3550 @ 3.07GHz, with 16381MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Wireshark decodes some valid RTP packets as STUN packets.
These STUN packets show up as "ChannelData TURN Message" packets.
I do have the "Try to decode RTP outside of conversations" preference for RTP
set.
According to Guy Harris: "This would either require a stronger TURN heuristic
or a way to disable the TURN heuristic."
In the attached example.pcap, two RTP packets get decoded as STUN: packets #
182 and 1637.
The same behavior first observed in wireshark 1.12.2.
You are receiving this mail because:
- You are watching all bug changes.