VDB

CVE-2019-12749

CVE-2019-12749 PUBLISHED CVSS 7.1 HIGH

Reported by mitre · Published June 11, 2019

dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only affects the DBUS_COOKIE_SHA1 authentication mechanism.) A malicious client with write access to its own home directory could manipulate a ~/.dbus-keyrings symlink to cause a DBusServer with a different uid to read and write in unintended locations. In the worst case, this could result in the DBusServer reusing a cookie that is known to the malicious client, and treating that cookie as evidence that a subsequent client connection came from an attacker-chosen uid, allowing authentication bypass.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
dbusAlpine1.12.16-r0, 1.10.28-r0
dbus-docAmazon Linux1:1.10.24-7.amzn2.0.2
dbus-testsAmazon Linux1:1.10.24-7.amzn2.0.2
dbus-develAmazon Linux1:1.10.24-7.amzn2.0.2
dbusfreedesktop1.13.12, 1.12.16, 1.10.28
dbusUbuntu:Pro:14.04:LTS1.6.18-0ubuntu4.5+esm1
dbusUbuntu:18.04:LTS1.12.2-1ubuntu1.1

Risk scores

CVSS 3.1
7.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

VendorProductVersions
n/an/an/a
alpinedbus0, 0
amazon:2dbus-doc0
amazon:2dbus-tests0
amazon:2dbus-devel0
n/an/a*
amazon:2dbus-libs0
amazon:2dbus0
amazon:2dbus-x110
archdbus0

Timeline

  • Jun 11, 2019 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Mar 1, 2024 PoC Published (3 in total, the first dated here)
  • Feb 17, 2026 CVE Updated
  • Mar 6, 2026 Distribution Patch (7 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (15 in total, the first dated here)
  • Sep 15, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2019-12749
vulnetix vdb fixes CVE-2019-12749

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2019-12749/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›