Skip to content
Fencer Vulns
medium 4.6

CVE-2008-0595 json

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…

published 2008-02-29 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-0605

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

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.

Patch / fix

  • freedesktop dbus 1.0.3, 1.1.20
  • dbus Debian 14, Debian 13, Debian 12 1.1.20-1

debian advisories DEBIAN-CVE-2008-0595

  • dbus RHEL 5 1.0.0-6.3.el5_1
  • dbus-x11 RHEL 5 1.0.0-6.3.el5_1

red hat advisories RHSA-2008:0159

  • dbus-1 openSUSE Tumbleweed 1.12.20-5.5

opensuse advisories openSUSE-SU-2024:10711-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-0595 updated

dbus security policy circumvention

  • Red Hat Enterprise Linux (v. 5 server) dbus 1.0.0-6.3.el5_1, dbus-x11 1.0.0-6.3.el5_1 Red Hat Enterprise Linux Desktop (v. 5 client) dbus 1.0.0-6.3.el5_1, dbus-x11 1.0.0-6.3.el5_1 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) dbus 1.0.0-6.3.el5_1, dbus-x11 1.0.0-6.3.el5_1
    fixed: vendor fix RHSA-2008:0159

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.