Skip to content
Fencer Intel
low 2.1

CVE-2014-3637 json

D-Bus 1.3.0 through 1.6.x before 1.6.24 and 1.8.x before 1.8.8 does not properly close connections for processes that have terminated, whic…

published 2014-09-22 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-3595

cvss
2.1
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 39%
public exploits
0
none known

Summary

D-Bus 1.3.0 through 1.6.x before 1.6.24 and 1.8.x before 1.8.8 does not properly close connections for processes that have terminated, which allows local users to cause a denial of service via a D-bus message containing a D-Bus connection file descriptor.

Patch / fix

  • dbus Debian 14, Debian 13, Debian 12 1.8.8-1

debian advisories DEBIAN-CVE-2014-3637

  • dbus Ubuntu 14.04 LTS 1.6.18-0ubuntu4.2

ubuntu advisories UBUNTU-CVE-2014-3637

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • dbus-1 openSUSE Tumbleweed 1.10.12-2.1

opensuse advisories openSUSE-SU-2024:10517-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-2014-3637 updated cvss 2.1

dbus: denial of service by creating unkillable D-Bus connections

  • Red Hat Enterprise Linux 5 dbus
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 dbus, dbus-x11, dbus-libs, dbus-tests
    affected: no fix available
  • Red Hat Enterprise Linux 6 dbus, dbus-x11, dbus-libs
    under investigation

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.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Intel 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.