Wireshark-bugs: [Wireshark-bugs] [Bug 9618] New: Invalid utf8 causes JSON dissector assertion fa
Date: Tue, 07 Jan 2014 09:13:11 +0000
Bug ID 9618
Summary Invalid utf8 causes JSON dissector assertion failure "g_utf8_validate"
Classification Unclassified
Product Wireshark
Version 1.10.2
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter magnus.reftel@gmail.com

Created attachment 12430 [details]
Excerpt of packet trace shoing the assertion failure

Build Information:
Version 1.10.2 (SVN Rev 51934 from /trunk-1.10)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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+ 3.8.4, with Cairo 1.12.16, with Pango 1.32.5, with
GLib 2.37.7, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.1, without
Python,
with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Oct  8 2012 16:37:35), with AirPcap.

Running on Linux 3.11.0-14-generic, with locale en_US.UTF-8, with libpcap
version 1.4.0, with libz 1.2.8, GnuTLS 2.12.23, Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz

Built using gcc 4.8.1.

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
When decoding a JSON message with a member name that is a UTF-8 string that has
been trunkated in the middle of a multi-byte sequence (in my specific case: e2
85 9c ec b7 94 ed bf ba e3 83 9b eb 8a 91 e4 b5 be ed 85), the following
message is shown in the frame dissection tree after the "JavaScritp Object
Notation" item:

[Dissector bug, protocol JSON: proto.c:2554: failed assertion
"g_utf8_validate(value, -1, ((void *)0))"]


You are receiving this mail because:
  • You are watching all bug changes.