Bug 2006285 (CVE-2021-20315) - CVE-2021-20315 gnome-shell: locking protection bypass allow unauthorized user to kill existing applications or start new ones
Summary: CVE-2021-20315 gnome-shell: locking protection bypass allow unauthorized user...
Alias: CVE-2021-20315
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1999758 2006699
Blocks: 2002738 2006774
TreeView+ depends on / blocked
Reported: 2021-09-21 11:56 UTC by Marian Rehak
Modified: 2022-10-02 21:52 UTC (History)
7 users (show)

Fixed In Version: gnome-shell 3.32.2-40.el8
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Last Closed: 2021-11-10 01:51:02 UTC

Attachments (Terms of Use)

Description Marian Rehak 2021-09-21 11:56:19 UTC
When locking the screen the application menu bar and the window list at the bottom of the screen are visible. The user has the ability to kill open windows and also start applications when the machine is locked.

Comment 1 Riccardo Schirone 2021-09-21 15:33:23 UTC

Comment 3 Riccardo Schirone 2021-09-21 15:43:24 UTC
This issue was only ever present in Centos 8 Stream, in particular in gnome-shell-3.32.2-39.el8.x86_64 . No released RHEL version was ever affected by this.

Comment 6 Riccardo Schirone 2021-09-22 08:25:40 UTC
This issue was introduced as part of backporting the feature in https://bugzilla.redhat.com/show_bug.cgi?id=1651378 .

Comment 10 Product Security DevOps Team 2021-11-10 01:51:00 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.