| Bug ID |
11758
|
| Summary |
Dbus dissector handles basic type alignment incorrectly.
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86-64
|
| OS |
Debian
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Wireshark 2.1.0 (v2.1.0rc0-640-g0ae1965 from master)
Copyright 1998-2015 Gerald Combs <[email protected]> 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.5.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.8, with GLib 2.46.1, with SMI 0.4.8, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 3.3.18, with Gcrypt 1.6.4, with MIT Kerberos,
with GeoIP, without QtMultimedia, without AirPcap.
Running on Linux 4.2.0-1-amd64, with locale C, with libpcap version 1.7.4, with
libz 1.2.8, with GnuTLS 3.3.18, with Gcrypt 1.6.4.
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (with SSE4.2)
Built using gcc 5.2.1 20151028.
--
The D-Bus specification has a whole section dedicated to how types must be
aligned in a D-Bus message. Padding must be inserted before values are
written.
Currently, the code do not handle alignment for basic types, except for strings
where padding is inserted at the end.
The attached pcap illustrate the problem. It is generated by filtering the
output of dbus-monitor --pcap with these invocations of dbus-send:
dbus-send --session --dest=non.existent / non.existent.Method byte:124
double:1234.0 byte:124 boolean:true byte:124 uint16:0x1234
dbus-send --session --dest=non.existent / non.existent.Method string:"some
bytes right after end of string" byte:33 byte:33 byte:33
dbus-send --session --dest=non.existent / non.existent.Method byte:124
string:"strings must be aligned too!"
You are receiving this mail because:
- You are watching all bug changes.
