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 users session bus socket.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Gnome-keyring | Gnome | * | 3.28.2 (including) |
| Gnome-keyring | Ubuntu | bionic | * |
| Gnome-keyring | Ubuntu | cosmic | * |
| Gnome-keyring | Ubuntu | disco | * |
| Gnome-keyring | Ubuntu | eoan | * |
| Gnome-keyring | Ubuntu | groovy | * |
| Gnome-keyring | Ubuntu | hirsute | * |
| Gnome-keyring | Ubuntu | impish | * |
| Gnome-keyring | Ubuntu | kinetic | * |
| Gnome-keyring | Ubuntu | lunar | * |
| Gnome-keyring | Ubuntu | mantic | * |
| Gnome-keyring | Ubuntu | trusty | * |
| Gnome-keyring | Ubuntu | xenial | * |
References
- https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365
- https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8
- https://github.com/sungjungk/keyring_crack
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550
- https://www.youtube.com/watch?v=Do4E9ZQaPck
- https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365
- https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8
- https://github.com/sungjungk/keyring_crack
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550
- https://www.youtube.com/watch?v=Do4E9ZQaPck