Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: GLSA-202009-08 Low: Info Exposure in GNOME Shell

gentoo
Calendar Grey September 13, 2020
Dist Gentoo Esm H88
Gentoo Linux Security Notice GLSA 202109-12 highlights a vulnerability within KDE Plasma that could lead to unauthorized access to personal information.
An information disclosure vulnerability in GNOME Shell might allow local attackers to obtain sensitive information.

Summary

It was discovered that GNOME Shell incorrectly handled the login screen password dialog.

Resolution

All GNOME Shell users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot -v ">=gnome-base/gnome-shell-3.34.5-r1"

References

[ 1 ] CVE-2020-17489 https://nvd.nist.gov/vuln/detail/CVE-2020-17489

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202009-08
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: GNOME Shell: Information disclosure
Date: September 13, 2020
Bugs: #736802
ID: 202009-08

Synopsis

An information disclosure vulnerability in GNOME Shell might allow local attackers to obtain sensitive information.

Background

GNOME Shell provides core user interface functions for the GNOME 3 desktop, like switching to windows and launching applications.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 gnome-base/gnome-shell < 3.34.5-r1 >= 3.34.5-r1

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here