Security readout for executives and security teams
Plain-English summary
A local user with access to an affected GNOME login screen could trigger an account-setup flow that should not run. On Ubuntu, and possibly derivatives, this could be chained with another issue to create a new privileged account. This is a high-risk local privilege escalation issue, not a remote internet attack.
Executive priority
Treat this as a high-priority workstation and shared-system patching issue. It is not internet-facing by itself, but successful exploitation could produce privileged local access and full system compromise.
Technical view
Affected gdm3 versions before 3.36.2 or 3.38.2 may start gnome-initial-setup when accountsservice is not reachable over D-Bus quickly enough. The CVSS vector indicates physical access, low complexity, low privileges, user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on Ubuntu or derivative desktop systems using affected GDM3 3.36 or 3.38 builds. Systems without local users or graphical login exposure are less likely to be reachable, but package inventory should confirm this rather than assume safety.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires local or physical access and user interaction, and the Ubuntu impact depends on chaining with an additional issue.
Researcher notes
The root issue is exceptional-condition handling: delayed D-Bus contact with accountsservice incorrectly opens the initial setup path. Public evidence names affected GDM3 versions and Ubuntu chaining risk, but this bundle does not establish active exploitation.
Mitigation direction
- Upgrade gdm3 to 3.36.2, 3.38.2, or a vendor-fixed package.
- Check Ubuntu and GNOME advisories for distribution-specific fixed versions.
- Prioritize shared workstations, kiosks, labs, and systems with many local users.
- Limit physical console access until affected systems are updated.
- Review privileged local accounts created during the exposure window.
Validation and detection
- Inventory systems running GNOME Display Manager or the gdm3 package.
- Confirm installed gdm3 versions are not before 3.36.2 or 3.38.2.
- Identify Ubuntu or derivative systems with graphical login enabled.
- Review local administrator accounts for unexpected additions.
- Check vendor security notes for package-specific remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-16125 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H0.56Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.gnome.org/GNOME/gdm/-/issues/642CVE reference · x_refsource_MISC
- https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1900314CVE reference · x_refsource_MISC
- https://securitylab.github.com/advisories/GHSL-2020-202-gdm3-LPE-unresponsive-accounts-daemonCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.