Gnome ShellApplication · Gnome

CVE-2021-20315

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 3.32.2 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A locking protection bypass flaw was found in some versions of gnome-shell as shipped within CentOS Stream 8, when the "Application menu" or "Window list" GNOME extensions are enabled. This flaw allows a physical attacker who has access to a locked system to kill existing applications and start new ones as the locked user, even if the session is still locked.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A locking protection bypass vulnerability in gnome-shell allows a physically present attacker to kill running applications and launch new ones as the locked user when the 'Application menu' or 'Window list' GNOME extensions are enabled, bypassing the session lock screen.

MitigationDisable the 'Application menu' and 'Window list' GNOME extensions until gnome-shell is patched, and apply available security updates for CentOS Stream 8.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gnome ShellApplication
Affected:< 3.32.2
StreamOperating system
Affected:= 8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed gnome-shell version
    Run `gnome-shell --version` or look up the package version using your package manager (e.g., `rpm -q gnome-shell`)
    Affected if Version is below 3.32.2, or on CentOS Stream 8 with gnome-shell installed
  2. Identify the OS distribution and version
    Check if the system is CentOS Stream 8 using `cat /etc/os-release` or `cat /etc/centos-release`
    Affected if System is CentOS Stream 8 with gnome-shell installed
  3. Determine if Application Menu extension is enabled
    Open GNOME Extensions app, or check via command line using `gsettings get org.gnome.shell enabled-extensions` to see if '[email protected]' or similar app-menu extension appears in the list
    Affected if The Application Menu extension appears in the enabled extensions list
  4. Determine if Window List extension is enabled
    Open GNOME Extensions app, or check via command line using `gsettings get org.gnome.shell enabled-extensions` to see if '[email protected]' or similar window-list extension appears in the list
    Affected if The Window List extension appears in the enabled extensions list

You are affected if gnome-shell version is below 3.32.2 (or you are on CentOS Stream 8) AND either the Application menu or Window list extension is enabled on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.32.2 or later
Fixed in 3.32.2
Interim mitigation

Disable the 'Application menu' and 'Window list' GNOME extensions until gnome-shell is patched, and apply available security updates for CentOS Stream 8.

Recommended fix High confidence

GNOME Shell 3.32.2 or later (via CentOS Stream 8 package update)

  1. Update system packages: dnf update gnome-shell (or yum update gnome-shell)
  2. After the update completes, verify the installed version: rpm -q gnome-shell
  3. Restart the GNOME session or reboot the system to apply the update
  4. Confirm the system is running GNOME Shell version 3.32.2 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gnome Shell Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20315 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data