VulnerabilityPublished 21 Sep 2022Updated 27 May 2025

CVE-2022-23949: keylime · CWE-290

Affects keylimeSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 6.3.0 soon.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.3.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade keylime to 6.3.0.

Affected software

Product	Affected	Fixed in
PyPIkeylime`pkg:pypi/keylime`Other threats	Affected <6.3.0	Fixed in 6.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2022-23949, European organizations should take the following specific actions: 1) Upgrade Keylime installations to version 6.3.0 or later, where the vulnerability has been addressed by sanitizing UUID inputs. 2) Implement strict input validation and sanitization controls at the application layer to reject malformed or suspicious UUIDs before processing. 3) Enhance logging infrastructure to include cryptographic integrity checks or append-only log mechanisms to detect and prevent log tampering. 4) Deploy anomaly detection tools that monitor log patterns for inconsistencies or suspicious entries indicative of spoofing attempts. 5) Restrict agent registration and communication to authenticated and authorized entities using strong mutual authentication mechanisms, such as TLS with client certificates, to reduce the risk of rogue agents. 6) Conduct regular audits of logs and attestation results to identify discrepancies early. 7) Incorporate Keylime vulnerability awareness into incident response plans to ensure rapid detection and containment if exploitation is suspected. 8) Engage with the Keylime community or vendor for any additional patches or security advisories. These measures go beyond generic advice by focusing on both immediate patching and strengthening the overall security posture around Keylime deployments.

Description

In Keylime before 6.3.0, unsanitized UUIDs can be passed by a rogue agent and can lead to log spoofing on the verifier and registrar.

Impact

For European organizations utilizing Keylime for remote attestation and integrity verification in cloud or edge environments, this vulnerability poses a significant risk. Log spoofing can undermine the trustworthiness of security logs, which are critical for incident detection, forensic analysis, and compliance reporting under regulations such as GDPR and NIS Directive. Attackers exploiting this vulnerability could conceal unauthorized activities, making it difficult for security teams to detect breaches or data exfiltration. The confidentiality impact is high, as indicated by the CVSS score, meaning sensitive information could be exposed or manipulated indirectly through log tampering. This can lead to regulatory non-compliance, reputational damage, and potential financial penalties. Since Keylime is often deployed in environments requiring high assurance of system integrity, such as government, finance, and critical infrastructure sectors, the impact is amplified. The vulnerability does not affect integrity or availability directly but compromises the reliability of security monitoring, which is a foundational component of cybersecurity defense. European organizations relying on Keylime should consider this vulnerability a priority for remediation to maintain operational security and compliance.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 02:10 UTC

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats