Bug ID: 12922
Summary: TLS padding extension dissector length parsing bug
OS: Linux (other)
Component: Dissection engine (libwireshark)
Created attachment 14930
client hello with padding extension
Copyright 1998-2016 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
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+ 3.20.9, with Cairo 1.14.6, with Pango 1.40.1, with
libpcap, with POSIX capabilities (Linux), with libnl 3, with libz 1.2.8, with
GLib 2.48.1, without SMI, with c-ares 1.11.0, with Lua 5.2, with GnuTLS 3.4.14,
with Gcrypt 1.7.3, with MIT Kerberos, with GeoIP, with PortAudio V19-devel
(built Dec 6 2015 12:27:18), without AirPcap.
Running on Linux 4.7.3-2-ARCH, with locale en_GB.UTF-8, with libpcap version
1.7.4, with libz 1.2.8, with GnuTLS 3.4.15, with Gcrypt 1.7.3.
Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (with SSE4.2)
Built using gcc 6.1.1 20160802.
Wireshark is Open Source Software released under the GNU General Public
Check the man page and http://www.wireshark.org for more information.
The padding dissector expects the padding extension payload to carry length
while the RFC 7685 states that a correct encoding of extension should include
only zero bytes in extension_data.
Because of that, bytes in the padding extension are interpreted as zero length
You are receiving this mail because:
You are watching all bug changes.
Sent via: Wireshark-bugs mailing list <email@example.com>