Skip to content
Fencer Vulns
medium 4.6

CVE-2008-4311 json

The default configuration of system.conf in D-Bus (aka DBus) before 1.2.6 omits the send_type attribute in certain rules, which allows loca…

published 2008-12-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4292

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 35%
public exploits
0
none known

Summary

The default configuration of system.conf in D-Bus (aka DBus) before 1.2.6 omits the send_type attribute in certain rules, which allows local users to bypass intended access restrictions by (1) sending messages, related to send_requested_reply; and possibly (2) receiving messages, related to receive_requested_reply.

Patch / fix

  • dbus Debian 14, Debian 13, Debian 12 1.2.1-5

debian advisories DEBIAN-CVE-2008-4311

  • PackageKit openSUSE Tumbleweed 1.2.2-13.2
  • dbus-1 openSUSE Tumbleweed 1.12.20-5.5
  • yast2-core openSUSE Tumbleweed 4.4.0-1.4

opensuse advisories openSUSE-SU-2024:10605-1openSUSE-SU-2024:10711-1openSUSE-SU-2024:11531-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-4311 updated

dbus: incorrect use of [send|receive]_requested_reply policy rule attribute in system.conf

  • Red Hat Enterprise Linux 4 dbus Red Hat Enterprise Linux 5 dbus
    affected: no fix planned “Will not fix”

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.41% chance of exploitation in the next 30 days, higher than 35% 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.