CVE-2018-19358 json
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…
published 7y ago modified 4mo ago also EUVD-2018-11054
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
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. 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.
Is CVE-2018-19358 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-19358 updated cvss 5.5
gnome-keyring: login credentials retrieval via a Secret Service API call
-
Red Hat Enterprise Linux 5 gnome-keyring Red Hat Enterprise Linux 6 gnome-keyring, gnome-keyring-pam Red Hat Enterprise Linux 7 gnome-keyring, gnome-keyring-pam Red Hat Enterprise Linux 8 gnome-keyring, gnome-keyring-pamnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.launchpad.net https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/sungjungk/keyring_crack referenced PoC, tagged "exploit" by a source, unverified
- youtube.com https://www.youtube.com/watch?v=Do4E9ZQaPck referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
References
-
bugs.launchpad.net
/ubuntu/+source/gnome-keyring/+bug/1780365
exploit, issue-tracking, third-party-advisory
-
github.com
/sungjungk/keyring_crack
exploit, third-party-advisory
-
youtube.com
/watch?v=Do4E9ZQaPck
exploit, third-party-advisory
- gitlab.gnome.org /GNOME/gnome-keyring/-/issues/5#note_1876550
- bugzilla.redhat.com /show_bug.cgi?id=1652194#c8
Sources
- CVE List CVE-2018-19358
- NVD CVE-2018-19358
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.