ghsa-2hpj-v4f4-7g4j
Vulnerability from github
Published
2022-05-24 16:47
Modified
2024-12-06 15:31
Severity ?
7.1 (High) - CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Details

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.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2019-12749",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-59",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2019-06-11T17:29:00Z",
      severity: "HIGH",
   },
   details: "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.",
   id: "GHSA-2hpj-v4f4-7g4j",
   modified: "2024-12-06T15:31:17Z",
   published: "2022-05-24T16:47:45Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2019-12749",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2019:1726",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2019:2868",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2019:2870",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2019:3707",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2019/06/msg00005.html",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2CQF37O73VH2JDVX2ILX2KD2KLXLQOU",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V2CQF37O73VH2JDVX2ILX2KD2KLXLQOU",
      },
      {
         type: "WEB",
         url: "https://seclists.org/bugtraq/2019/Jun/16",
      },
      {
         type: "WEB",
         url: "https://security.gentoo.org/glsa/201909-08",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20241206-0010",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4015-1",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4015-2",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2019/dsa-4462",
      },
      {
         type: "WEB",
         url: "https://www.openwall.com/lists/oss-security/2019/06/11/2",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00059.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00092.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00026.html",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2019/06/11/2",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/108751",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.