First published: Sun Nov 18 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>
Credit: cve@mitre.org
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.
CVE-2018-19358 has a moderate severity level due to the potential for unauthorized access to sensitive login credentials.
To fix CVE-2018-19358, update GNOME Keyring to version 3.28.3 or later where the vulnerability is addressed.
CVE-2018-19358 affects local users of GNOME Keyring versions up to 3.28.2 who have the keyring unlocked.
CVE-2018-19358 cannot be exploited remotely as it requires local access to the vulnerable system.
The impacts of CVE-2018-19358 include the possibility of leaking sensitive credentials stored in the GNOME Keyring.