CVE-2018-19358

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:gnome:gnome-keyring:*:*:*:*:*:*:*:*

History

21 Nov 2024, 03:57

Type Values Removed Values Added
References () https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365 - Exploit, Issue Tracking, Third Party Advisory () https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365 - Exploit, Issue Tracking, Third Party Advisory
References () https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8 - () https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8 -
References () https://github.com/sungjungk/keyring_crack - Exploit, Third Party Advisory () https://github.com/sungjungk/keyring_crack - Exploit, Third Party Advisory
References () https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550 - () https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550 -
References () https://www.youtube.com/watch?v=Do4E9ZQaPck - Exploit, Third Party Advisory () https://www.youtube.com/watch?v=Do4E9ZQaPck - Exploit, Third Party Advisory

07 Nov 2023, 02:55

Type Values Removed Values Added
Summary ** DISPUTED ** 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. 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.

23 Oct 2023, 16:15

Type Values Removed Values Added
References
  • (MISC) https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8 -
  • (MISC) https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550 -
Summary 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. ** DISPUTED ** 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.

Information

Published : 2018-11-18 19:29

Updated : 2024-11-21 03:57


NVD link : CVE-2018-19358

Mitre link : CVE-2018-19358

CVE.ORG link : CVE-2018-19358


JSON object : View

Products Affected

gnome

  • gnome-keyring