CVE-2020-35512

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

A use-after-free flaw was found in D-Bus Development branch <= 1.13.16, dbus-1.12.x stable branch <= 1.12.18, and dbus-1.10.x and older branches <= 1.10.30 when a system has multiple usernames sharing the same UID. When a set of policy rules references these usernames, D-Bus may free some memory in the heap, which is still used by data structures necessary for the other usernames sharing the UID, possibly leading to a crash or other undefined behaviors

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 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.3%
EPSS %ILE
24th
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

February 15, 2021

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 3, 2026
Patch available. Sources: redhat.
generic

CVE-2020-35512

https://security-tracker.debian.org/tracker/CVE-2020-35512
generic

Dangling pointer access in dbus-userdb.c (#305) · Issues · dbus / dbus · GitLab

https://gitlab.freedesktop.org/dbus/dbus/-/issues/305#note_829128
redhat

1909101 – (CVE-2020-35512) CVE-2020-35512 dbus: users with the same numeric UID could lead to use-after-free and undefined behaviour

https://bugzilla.redhat.com/show_bug.cgi?id=1909101
generic

755392 – (CVE-2020-35512) <sys-apps/dbus-1.12.20: use after free if duplicate UIDs (CVE-2020-35512)

https://bugs.gentoo.org/755392

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibdbus-1-3 (1.12.16-2ubuntu2.2) @ focal2026-05-26ubuntu
ubuntulibdbus-1-dev (1.10.6-1ubuntu3.6+esm1) @ xenial2026-05-26ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.20-1: fixed in 1.12.20-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.20-1: fixed in 1.12.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.20-1: fixed in 1.12.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dbus—
  • every version up to 1.12.20-1: fixed in 1.12.20-1
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2020-35512?
CVE-2020-35512 is a high vulnerability published on February 15, 2021. A use-after-free flaw was found in D-Bus Development branch <= 1.13.16, dbus-1.12.x stable branch <= 1.12.18, and dbus-1.10.x and older branches <= 1.10.30 when a system has multiple usernames sharing the same UID. When a set of policy rules references these usernames, D-Bus may free some memory in…
When was CVE-2020-35512 disclosed?
CVE-2020-35512 was first published on February 15, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-35512 actively exploited?
CVE-2020-35512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-35512?
CVE-2020-35512 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2020-35512?
A fix for CVE-2020-35512 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-35512

Explore →

Is Your Infrastructure Affected by CVE-2020-35512?

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

Book a Demo →Browse All CVEs