First published: Wed Nov 21 2018(Updated: )
GNOME Keyring through 3.28.2 allows local users to retrieve login credentials via a Secret Service API call and the D-Bus interface if the keyring is unlocked, a similar issue to <a href="https://access.redhat.com/security/cve/CVE-2008-7320">CVE-2008-7320</a>. One perspective is that this occurs because available D-Bus protection mechanisms (involving the busconfig and policy XML elements) are not used. References: <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365">https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365</a>
Affected Software | Affected Version | How to fix |
---|---|---|
GNOME Keyring | <=3.28.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1652194 is considered critical due to the potential for unauthorized access to sensitive login credentials.
To fix REDHAT-BUG-1652194, ensure that GNOME Keyring is updated to a version later than 3.28.2.
Local users who have access to an unlocked GNOME Keyring 3.28.2 are affected by REDHAT-BUG-1652194.
An attacker can retrieve sensitive login credentials via the Secret Service API if they have access to an unlocked keyring.
A temporary workaround for REDHAT-BUG-1652194 is to lock the GNOME Keyring when not in use to prevent unauthorized access.