CVE-2011-2200: Input Validation

Published Jun 12, 2011
·
Updated

It was found that D-BUS message bus service / messaging facility did not update the byte-order flag of the message properly by swapping the byte order of incoming messages into their native endiannes. A local, authenticated user could use this flaw to send a specially-crafted message to a system service (like Avahi or NetworkManager), using the system bus, potentially leading to disconnect of such a service from system bus (denial of service).

References: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629938 [2] https://bugs.freedesktop.org/showbug.cgi?id=38120

Upstream patches: [3] http://cgit.freedesktop.org/dbus/dbus/commit/?h=dbus-1.2&id=6519a1f77c61d753d4c97efd6e15630eb275336e (in upstream v1.2.28 version)

[4] http://cgit.freedesktop.org/dbus/dbus/commit/?h=dbus-1.4&id=c3223ba6c401ba81df1305851312a47c485e6cd7 (in upstream v1.4.12 version)

Other sources

The dbusheaderbyteswap function in dbus-marshal-header.c in D-Bus (aka DBus) 1.2.x before 1.2.28, 1.4.x before 1.4.12, and 1.5.x before 1.5.4 does not properly handle a non-native byte order, which allows local users to cause a denial of service (connection loss), obtain potentially sensitive information, or conduct unspecified state-modification attacks via crafted messages.

MITRE

Affected Software

52 affected componentsFixes available
redhat/dbus<1.1.28
1.1.28
redhat/dbus<1.4.12
1.4.12
redhat/dbus<1.5.4
1.5.4
D-bus Project D-bus=1.5.0
D-bus Project D-bus=1.5.2
D-bus Project D-bus=1.4.8
D-bus Project D-bus=1.4.1
D-bus Project D-bus=1.4.0
D-bus Project D-bus=1.4.6
D-bus Project D-bus=1.4.10
D-bus Project D-bus=1.4.4
D-bus Project D-bus=1.2.4.2
D-bus Project D-bus=1.2.1
D-bus Project D-bus=1.2.14
D-bus Project D-bus=1.2.4
D-bus Project D-bus=1.2.4.4
D-bus Project D-bus=1.2.2
D-bus Project D-bus=1.2.10
D-bus Project D-bus=1.2.8
D-bus Project D-bus=1.2.12
D-bus Project D-bus=1.2.26
D-bus Project D-bus=1.2.24
D-bus Project D-bus=1.2.22
D-bus Project D-bus=1.2.4.6
D-bus Project D-bus=1.2.6
D-bus Project D-bus=1.2.20
D-bus Project D-bus=1.2.16
D-bus Project D-bus=1.2.18
D-bus Project D-bus=1.2.3
Freedesktop dbus=1.5.0
Freedesktop dbus=1.5.2
Freedesktop dbus=1.4.0
Freedesktop dbus=1.4.1
Freedesktop dbus=1.4.4
Freedesktop dbus=1.4.6
Freedesktop dbus=1.4.8
Freedesktop dbus=1.4.10
Freedesktop dbus=1.2.1
Freedesktop dbus=1.2.2
Freedesktop dbus=1.2.3
Freedesktop dbus=1.2.4
Freedesktop dbus=1.2.6
Freedesktop dbus=1.2.8
Freedesktop dbus=1.2.10
Freedesktop dbus=1.2.12
Freedesktop dbus=1.2.14
Freedesktop dbus=1.2.16
Freedesktop dbus=1.2.18
Freedesktop dbus=1.2.20
Freedesktop dbus=1.2.22
Freedesktop dbus=1.2.24
Freedesktop dbus=1.2.26

Event History

Jun 22, 2011
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-2200?

CVE-2011-2200 has a high severity level as it can cause denial of service due to improper handling of non-native byte order.

2

How do I fix CVE-2011-2200?

To fix CVE-2011-2200, you should update D-Bus to version 1.2.28 or later for the 1.2.x series, 1.4.12 or later for the 1.4.x series, or 1.5.4 or later for the 1.5.x series.

3

What software versions are affected by CVE-2011-2200?

CVE-2011-2200 affects D-Bus versions prior to 1.2.28, 1.4.12, and 1.5.4.

4

Can CVE-2011-2200 be exploited remotely?

No, CVE-2011-2200 can only be exploited by local users.

5

What are the consequences of CVE-2011-2200?

The consequences of CVE-2011-2200 include denial of service, which may result in connection loss.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203