CVE-2019-12749

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 11, 2019

Last Modified

February 13, 2026

References (35)

Vendor Advisories for CVE-2019-12749(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibdbus-1-dev (1.10.6-1ubuntu3.4) @ xenial2026-05-27ubuntu
ubuntudbus-1-doc (1.6.18-0ubuntu4.5+esm1) @ trusty2026-05-27ubuntu
redhatopenshiftdo/odo-init-image-rhel7:1.1.3-22021-03-22redhat
redhatdbus-1:1.10.24-15.el72020-09-29redhat
redhatdbus-1:1.12.8-9.el82019-11-05redhat
redhatdbus-1:1.2.24-9.el6_52019-09-23redhat
redhatdbus-1:1.2.24-9.el6_62019-09-23redhat
redhatdbus-1:1.2.24-11.el6_102019-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(24 across 24 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.12.16-r0: fixed in 1.12.16-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.10.28-r0: fixed in 1.10.28-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.10.28-r0: fixed in 1.10.28-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • 1.12.0 up to 1.10.28-r0: fixed in 1.10.28-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.16-1: fixed in 1.12.16-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.16-1: fixed in 1.12.16-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.16-1: fixed in 1.12.16-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.16-1: fixed in 1.12.16-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
dbus1.8.16-1 ... 1.8.22-0+deb8u1 (7 versions)
  • every version up to 1.8.22-0+deb8u2: fixed in 1.8.22-0+deb8u2
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
dbus1.10.18-1 ... 1.10.26-0+deb9u1 (6 versions)
  • every version up to 1.10.28-0+deb9u1: fixed in 1.10.28-0+deb9u1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 163 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-09-30 14:59 UTCEPSS rescore
  5. 2026-09-30 10:10 UTCEG score recompute
  6. 2026-09-28 13:46 UTCEPSS rescore
  7. 2026-09-28 03:32 UTCOSV refresh
  8. 2026-09-27 13:40 UTCEPSS rescore
  9. 2026-09-26 15:53 UTCEPSS rescore
  10. 2026-09-26 00:20 UTCEPSS rescore
  11. 2026-09-24 13:59 UTCEPSS rescore
  12. 2026-09-23 13:43 UTCEPSS rescore
  13. 2026-09-21 20:27 UTCEPSS rescore
  14. 2026-09-20 20:10 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-16 14:04 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-13 16:42 UTCEPSS rescore
  20. 2026-09-12 14:56 UTCEPSS rescore
  21. 2026-09-11 14:48 UTCEPSS rescore
  22. 2026-09-08 21:55 UTCEPSS rescore
  23. 2026-09-08 10:09 UTCOSV refresh
  24. 2026-09-07 15:57 UTCEPSS rescore
  25. 2026-09-06 13:44 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:24 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:02 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 03:32 UTCEPSS rescore
  6. 2026-08-30 19:13 UTCEPSS rescore
  7. 2026-08-30 01:18 UTCEPSS rescore
  8. 2026-08-28 21:36 UTCEPSS rescore
  9. 2026-08-27 14:21 UTCEPSS rescore
  10. 2026-08-26 14:42 UTCEPSS rescore
  11. 2026-08-25 13:45 UTCEPSS rescore
  12. 2026-08-21 23:45 UTCEPSS rescore
  13. 2026-08-21 20:44 UTCOSV refresh
  14. 2026-08-20 22:51 UTCEPSS rescore
  15. 2026-08-19 17:00 UTCEPSS rescore
  16. 2026-08-18 13:44 UTCEPSS rescore
  17. 2026-08-17 13:43 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-13 21:56 UTCEPSS rescore
  22. 2026-08-12 13:47 UTCEPSS rescore
  23. 2026-08-09 13:43 UTCEPSS rescore
  24. 2026-08-08 16:33 UTCEPSS rescore
  25. 2026-08-07 16:23 UTCEPSS rescore
  26. 2026-08-06 13:43 UTCEPSS rescore
  27. 2026-08-06 03:51 UTCOSV refresh
  28. 2026-08-05 19:13 UTCEPSS rescore
  29. 2026-08-04 15:05 UTCEPSS rescore
  30. 2026-08-04 10:33 UTCEPSS rescore
  31. 2026-08-03 10:31 UTCEPSS rescore
  32. 2026-08-02 02:23 UTCEPSS rescore
  33. 2026-08-01 04:12 UTCEPSS rescore
  34. 2026-07-30 16:24 UTCEPSS rescore
  35. 2026-07-30 01:27 UTCEPSS rescore
  36. 2026-07-28 15:32 UTCEPSS rescore
  37. 2026-07-26 14:51 UTCEPSS rescore
  38. 2026-07-25 14:14 UTCEPSS rescore
  39. 2026-07-24 14:14 UTCEPSS rescore
  40. 2026-07-24 14:14 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 01:39 UTCEG score recompute
  43. 2026-07-22 22:19 UTCEG score recompute
  44. 2026-07-22 14:05 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:04 UTCEPSS rescore
  48. 2026-07-20 15:02 UTCOSV refresh
  49. 2026-07-19 14:28 UTCEPSS rescore
  50. 2026-07-19 14:28 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-19 02:26 UTCEPSS rescore
  53. 2026-07-18 10:01 UTCEPSS rescore
  54. 2026-07-16 16:59 UTCEPSS rescore
  55. 2026-07-16 16:59 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-13 22:27 UTCEPSS rescore
  58. 2026-07-13 06:10 UTCEPSS rescore
  59. 2026-07-13 06:10 UTCEPSS rescore
  60. 2026-07-12 05:43 UTCEPSS rescore
  61. 2026-07-11 08:24 UTCEPSS rescore
  62. 2026-07-09 19:06 UTCEPSS rescore
  63. 2026-07-08 15:11 UTCEPSS rescore
  64. 2026-07-07 13:42 UTCEPSS rescore
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 02:20 UTCEPSS rescore
  67. 2026-07-05 02:27 UTCEPSS rescore
  68. 2026-07-04 06:28 UTCEPSS rescore
  69. 2026-07-04 06:28 UTCEPSS rescore
  70. 2026-07-03 09:56 UTCOSV refresh
  71. 2026-07-02 16:56 UTCEPSS rescore
  72. 2026-07-01 15:03 UTCEPSS rescore
  73. 2026-07-01 15:03 UTCEPSS rescore
  74. 2026-06-30 23:20 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-12749?
CVE-2019-12749 is a high vulnerability published on 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 DBUSCOOKIESHA1 in the libdbus…
When was CVE-2019-12749 disclosed?
CVE-2019-12749 was first published on June 11, 2019, with the most recent update on February 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-12749 actively exploited?
CVE-2019-12749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-12749?
CVE-2019-12749 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2019-12749?
A fix for CVE-2019-12749 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-12749 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-12749

Explore →

Is Your Infrastructure Affected by CVE-2019-12749?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs