CVE-2018-19358

Name	CVE-2018-19358
Description	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 CVE-2008-7320. One perspective is that this occurs because available D-Bus protection mechanisms (involving the busconfig and policy XML elements) are not used. NOTE: the vendor disputes this because, according to the security model, untrusted applications must not be allowed to access the user's session bus socket.
Source	CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs	914154

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
gnome-keyring (PTS)	bullseye	3.36.0-1	vulnerable
	bookworm	42.1-1	vulnerable
	sid, trixie	46.2-1	vulnerable

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
gnome-keyring	source	(unstable)	(unfixed)	unimportant		914154

Notes

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365
https://github.com/sungjungk/keyring_crack
The default keyring is automatically unlocked upon successful login.
The current behavior to access passwords via DBus is expected but
cannot be compromised by another user on the system. Users can choose
to use a separate keyring if they prefer to be prompted.
Non issue
https://wiki.gnome.org/Projects/GnomeKeyring/SecurityFAQ
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5