First published: Thu Apr 27 2017(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Gnome-shell | =3.22.0 | |
Gnome-shell | =3.22.1 | |
Gnome-shell | =3.22.2 | |
Gnome-shell | =3.22.3 | |
Gnome-shell | =3.23.1 | |
Gnome-shell | =3.23.2 | |
Gnome-shell | =3.23.3 | |
Gnome-shell | =3.23.90 | |
Gnome-shell | =3.23.91 | |
Gnome-shell | =3.23.92 | |
Gnome-shell | =3.24.0 | |
Gnome-shell | =3.24.1 | |
debian/gnome-shell | 3.38.6-1~deb11u2 43.9-0+deb12u2 48.0-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-8288 has a medium severity, as it allows unauthorized access to application information through enabled extensions on the lock screen.
To mitigate CVE-2017-8288, upgrade to gnome-shell version 3.38.6-1~deb11u2 or higher.
CVE-2017-8288 affects gnome-shell versions 3.22.0 to 3.24.1.
Users may inadvertently expose application information to unauthorized individuals due to extensions remaining enabled in the lock screen.
CVE-2017-8288 is primarily a client-side vulnerability affecting the gnome-shell user interface.