CVE Vulnerabilities


Incorrect Authorization

Published: Feb 29, 2008 | Modified: Feb 07, 2022
CVSS 3.x
CVSS 2.x

dbus-daemon in D-Bus before 1.0.3, and 1.1.x before 1.1.20, recognizes send_interface attributes in allow directives in the security policy only for fully qualified method calls, which allows local users to bypass intended access restrictions via a method call with a NULL interface.


The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affected Software

Name Vendor Start Version End Version
Fedora Fedoraproject 7 7
Mandrake_linux Mandrakesoft 2007 2007
Mandrake_linux Mandrakesoft 2007.0_x86_64 2007.0_x86_64
Mandrake_linux Mandrakesoft 2007.1 2007.1
Mandrake_linux Mandrakesoft 2007.1 2007.1
Mandrake_linux Mandrakesoft 2008.0 2008.0
Mandrake_linux Mandrakesoft 2008.0 2008.0
Enterprise_linux Redhat 5 5
Enterprise_linux Redhat 5.0 5.0
Red Hat Enterprise Linux 5 RedHat dbus-0:1.0.0-6.3.el5_1 *
Dbus Ubuntu dapper *
Dbus Ubuntu devel *
Dbus Ubuntu edgy *
Dbus Ubuntu feisty *
Dbus Ubuntu gutsy *
Dbus Ubuntu hardy *

Extended Description

Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.

Potential Mitigations

  • Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.