LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19358: GNOME Keyring through 3.28.2 allows local users to retrieve login credentials via a Secret Service API call...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE concerns GNOME Keyring exposing stored login credentials to a local user through the Secret Service API and D-Bus when the keyring is already unlocked. It is not described as a remote attack. Business risk is credential exposure on Linux desktops where untrusted local applications can run in the user session.

Executive priority

Treat this as a targeted desktop credential-exposure risk, not a broad remote emergency. Prioritize managed Linux workstations handling privileged or sensitive credentials, especially where local application control is weak.

Technical view

GNOME Keyring through 3.28.2 is reported to allow local credential retrieval via Secret Service API calls over the D-Bus session interface when the keyring is unlocked. The vendor disputes the CVE, stating the security model assumes untrusted applications must not access the user's session bus socket.

Likely exposure

Exposure is most plausible on Linux desktop environments using GNOME Keyring through 3.28.2, especially where users run untrusted local applications or where session bus access is weakly controlled.

Exploitation context

The bundle references public demonstration or proof-of-concept material, but KEV is false and no cited source here states active exploitation. The described condition requires local user/session access and an unlocked keyring.

Researcher notes

Key uncertainty is vendor dispute and absent CVSS/CWE data. The practical boundary is the desktop trust model: whether local code in the user session should be trusted and whether it can reach D-Bus Secret Service interfaces.

Mitigation direction

  • Check GNOME, distro, and vendor guidance for affected package handling.
  • Update GNOME Keyring packages if your vendor provides a relevant fix.
  • Prevent untrusted applications from accessing user session bus sockets.
  • Limit execution of untrusted local software on Linux desktops.
  • Review endpoint controls for credential-store and D-Bus access abuse.

Validation and detection

  • Inventory systems running GNOME Keyring through 3.28.2.
  • Confirm whether keyrings unlock automatically during user login.
  • Assess whether untrusted local apps can run in user sessions.
  • Review vendor advisories for distro-specific disposition or dispute notes.
  • Monitor endpoints for unusual credential-store access patterns.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-19358 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.