CPE Details
GNOME gnome-shell 3.23.2
3.23.2
2019-11-05
18h35 +00:00
18h35 +00:00
2019-11-05
18h35 +00:00
18h35 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:gnome:gnome-shell:3.23.2:*:*:*:*:*:*:*
Informations
Vendor
gnomeProduct
gnome-shellVersion
3.23.2Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| 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. | 6.1 |
Medium |
||
| An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible for a brief moment upon a logout. (If the password were never shown in cleartext, only the password length is revealed.) | 4.3 |
Medium |
||
| It was discovered that the gnome-shell lock screen since version 3.15.91 did not properly restrict all contextual actions. An attacker with physical access to a locked workstation could invoke certain keyboard shortcuts, and potentially other actions. | 4.3 |
Medium |
||
| gnome-shell 3.22 through 3.24.1 mishandles extensions that fail to reload, which can lead to leaving extensions enabled in the lock screen. With these extensions, a bystander could launch applications (but not interact with them), see information from the extensions (e.g., what applications you have opened or what music you were playing), or even execute arbitrary commands. It all depends on what extensions a user has enabled. The problem is caused by lack of exception handling in js/ui/extensionSystem.js. | 8.1 |
High |
2025©
tesweb SA
