CVE-2019-12749 [High] | Spoofing in Dbus

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.05%	0.56%	+0.51%
2	2026-05-30	0.06%	0.05%	-0.01%
3	2026-05-28	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.05%

0.56%

+0.51%

2026-05-30

0.06%

0.05%

-0.01%

2026-05-28

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.8	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0
7.1	3.0	HIGH	`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.8	5.2	[email protected]
3.6	2.0	LOW	`AV:L/AC:L/Au:N/C:P/I:P/A:N` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	3.9	4.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.8

5.2

134c704f-9b21-4f2e-91b3-4a467353bcc0

7.1

3.0

HIGH

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.8

5.2

[email protected]

3.6

2.0

LOW

AV:L/AC:L/Au:N/C:P/I:P/A:N Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

3.9

4.9

[email protected]

OS Trackers for CVE-2019-12749

vendor	priority	summary	link
`alpine`	—	CVE-2019-12749: 1 source package rows (dbus); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0.	https://security.alpinelinux.org/vuln/CVE-2019-12749
`debian`	not yet assigned	CVE-2019-12749 not yet assigned priority: Debian including 1 source packages (dbus), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-12749
`gentoo`	normal	CVE-2019-12749: 1 GLSA(s) (201909-08), 1 atom(s) (sys-apps/dbus); latest impact normal.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-12749
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2019-12749
`suse`	medium	CVE-2019-12749 severity moderate: SUSE including 395 source package names (0.1.0:dbus-1-1.12.2-8.3.1, 0.1.0:libdbus-1-3-1.12.2-8.3.1, …), 687 product×package rows across 152 product lines (Container bci/bci-init, Container caasp/v4/cilium, … (152 product lines)): Fixed 548, Known Affected 139.	https://www.suse.com/security/cve/CVE-2019-12749/
`ubuntu`	medium	CVE-2019-12749 medium priority: Ubuntu including 1 source packages (dbus), 6 status rows across 6 suites (bionic, cosmic, disco, trusty, upstream, xenial): released 5, needs-triage 1.	https://ubuntu.com/security/CVE-2019-12749

Affected software / configurations for CVE-2019-12749

Vendor	Product	Version	Raw CPE
freedesktop	dbus	< 1.10.28	cpe:2.3:a:freedesktop:dbus::::::::
freedesktop	dbus	>= 1.12.0, < 1.12.16	cpe:2.3:a:freedesktop:dbus::::::::
freedesktop	dbus	>= 1.13.0, < 1.13.12	cpe:2.3:a:freedesktop:dbus::::::::
canonical	ubuntu_linux	16.04	cpe:2.3:o:canonical:ubuntu_linux:16.04::::lts:::
canonical	ubuntu_linux	18.04	cpe:2.3:o:canonical:ubuntu_linux:18.04::::lts:::
canonical	ubuntu_linux	18.10	cpe:2.3:o:canonical:ubuntu_linux:18.10:::::::*
canonical	ubuntu_linux	19.04	cpe:2.3:o:canonical:ubuntu_linux:19.04:::::::*

References for CVE-2019-12749

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00059.html
http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00092.html
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00026.html
http://www.openwall.com/lists/oss-security/2019/06/11/2	Mailing List Mitigation Third Party Advisory
http://www.securityfocus.com/bid/108751
https://access.redhat.com/errata/RHSA-2019:1726
https://access.redhat.com/errata/RHSA-2019:2868
https://access.redhat.com/errata/RHSA-2019:2870
https://access.redhat.com/errata/RHSA-2019:3707
https://lists.debian.org/debian-lts-announce/2019/06/msg00005.html
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2CQF37O73VH2JDVX2ILX2KD2KLXLQOU/
https://seclists.org/bugtraq/2019/Jun/16
https://security.gentoo.org/glsa/201909-08
https://usn.ubuntu.com/4015-1/	Third Party Advisory
https://usn.ubuntu.com/4015-2/
https://www.debian.org/security/2019/dsa-4462
https://www.openwall.com/lists/oss-security/2019/06/11/2	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20241206-0010/

URL

CVE-2019-12749

Exploit prediction scoring system (EPSS) score for CVE-2019-12749

Common vulnerability scoring system (CVSS) metrics for CVE-2019-12749

Weakness enumeration for CVE-2019-12749

OS Trackers for CVE-2019-12749

Affected software / configurations for CVE-2019-12749

References for CVE-2019-12749