Security readout for executives and security teams
Plain-English summary
Keylime versions before 6.3.0 did not sanitize agent UUID values, letting a rogue agent spoof or manipulate log entries on verifier and registrar components. The main business risk is loss of trustworthy attestation and audit evidence, not confirmed system takeover from the supplied sources.
Executive priority
Treat as high priority for environments relying on Keylime for attestation, compliance evidence, or incident response logs. Prioritize remediation where verifier and registrar logs influence security decisions or audit outcomes. Lower urgency may apply if Keylime is absent or isolated from untrusted agents.
Technical view
CVE-2022-23949 is a Keylime log-spoofing issue involving unsanitized UUIDs accepted from a rogue agent. Sources describe impact on verifier and registrar logging and classify it as high severity with CVSS 3.1 score 7.5. Fix evidence points to Keylime 6.3.0 and related upstream commits.
Likely exposure
Exposure is likely where Keylime verifier or registrar components run versions before 6.3.0 and accept agent registrations or communications. The supplied data does not identify specific operating system packages, distributions, hosted services, or downstream backports.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Practical abuse requires a rogue Keylime agent interacting with verifier or registrar components. The effect described is log spoofing, which can mislead monitoring, investigations, and trust decisions.
Researcher notes
Evidence supports a pre-6.3.0 Keylime issue involving UUID sanitization and log spoofing. The supplied sources do not prove remote code execution, privilege escalation, public exploit availability, or active exploitation. Affected downstream package ranges require separate vendor confirmation.
Mitigation direction
- Upgrade Keylime verifier and registrar deployments to 6.3.0 or later.
- Review the GitHub advisory before relying on downstream package status.
- Apply vendor or distribution backports where direct upstream upgrade is not used.
- Restrict Keylime agent enrollment to trusted systems and networks.
- Preserve existing logs before remediation for investigation integrity.
Validation and detection
- Inventory all Keylime verifier and registrar instances.
- Confirm deployed Keylime versions and package backport status.
- Check whether any instance runs a version before 6.3.0.
- Review verifier and registrar logs for suspicious or malformed agent UUID entries.
- Verify monitoring treats attestation logs as potentially untrusted before 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-290: 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-23949 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:H/I:N/A:N
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:H/I:N/A:N3.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:H/I:N/A:N
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-87gh-qc28-j9mmCVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/commit/387e320dc22c89f4f47c68cb37eb9eec2137f34bCVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/commit/e429e95329fc60608713ddfb82f4a92ee3b3d2d9CVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/commit/65c2b737129b5837f4a03660aeb1191ced275a57CVE 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.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.