Link Following Affecting libdbus-1-3-32bit package, versions <1.12.2-3.5.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.08% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES150-LIBDBUS1332BIT-2749571
  • published14 Apr 2022
  • disclosed17 Jun 2019

Introduced: 17 Jun 2019

CVE-2019-12749  (opens in a new tab)
CWE-59  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 libdbus-1-3-32bit to version 1.12.2-3.5.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libdbus-1-3-32bit package and not the libdbus-1-3-32bit package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

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.