Security readout for executives and security teams
Plain-English summary
Keylime’s revocation notifier used a predictable UNIX socket path under /tmp. In affected Keylime versions, an unprivileged local user could interfere with that path and prevent Keylime operations, disrupting attestation workflows. The provided sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Treat this as a high-priority availability issue for environments relying on Keylime for trust decisions. It can disrupt security operations, but the provided evidence does not indicate active exploitation or direct data compromise.
Technical view
CVE-2022-23950 is a CWE-379 availability flaw in Keylime before 6.3.0. The revocation notifier used a fixed /tmp path for its UNIX domain socket, allowing unprivileged users to block normal operation. CVSS 3.1 is 7.5, with high availability impact and no confidentiality or integrity impact stated.
Likely exposure
Exposure is most relevant where Keylime is deployed for measured boot, runtime integrity, or attestation services on multi-user systems. The bundle indicates Keylime before 6.3.0 is affected; confirm exact installed versions against the vendor advisory.
Exploitation context
The described abuse requires access as an unprivileged local user, despite the CVSS vector in the bundle being network-based. The sources support denial of Keylime operations, not data theft or privilege escalation. No active exploitation evidence is provided.
Researcher notes
The source bundle has one ambiguity: the description says before 6.3.0, while the affected entry lists keylime 6.3.0. Use the GitHub advisory and fixing commit as authoritative references before closing exposure.
Mitigation direction
- Upgrade Keylime to 6.3.0 or later per the advisory context.
- Review the Keylime GitHub advisory for exact fixed-version guidance.
- Prioritize systems where untrusted local users can access the host.
- Monitor vendor guidance for distribution-specific patched packages.
- Restrict unnecessary local user access on Keylime hosts.
Validation and detection
- Inventory Keylime installations and record exact versions.
- Confirm whether revocation notifier is enabled or used operationally.
- Check vendor advisory and commit references against deployed packages.
- Review logs for revocation notifier startup or socket errors.
- Validate attestation and revocation workflows after patching.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-379: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-23950 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://seclists.org/oss-sec/2022/q1/101CVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/security/advisories/GHSA-9r9r-f8xc-m875CVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/commit/ea5d0373fa2c050d5d95404eb779be7e8327b911CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Creation of Temporary File in Directory with Insecure Permissions
Creation of Temporary File in Directory with Insecure Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.