Skip to content

Tenant and Verifier might not use the same registrar data

Critical severity GitHub Reviewed Published May 4, 2022 in keylime/keylime • Updated Sep 2, 2023

Package

pip keylime (pip)

Affected versions

< 6.4.0

Patched versions

6.4.0

Description

Keylime does not enforce that the agent registrar data is the same when the tenant uses it for validation of the EK and identity quote and the verifier for validating the integrity quote. This allows an attacker to use one AK, EK pair from a real TPM to pass EK validation and give the verifier an AK of a software TPM. A successful attack breaks the entire chain of trust because a not validated AK is used by the verifier. This issue is worse if the validation happens first and then the agent gets added to the verifier because the timing is easier and the verifier does not validate the regcount entry being equal to 1. At this time, there are no known workaround.

References

@mpeters mpeters published to keylime/keylime May 4, 2022
Published to the GitHub Advisory Database May 5, 2022
Reviewed May 5, 2022
Published by the National Vulnerability Database May 6, 2022
Last updated Sep 2, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.199%
(58th percentile)

Weaknesses

CVE ID

CVE-2022-1053

GHSA ID

GHSA-jf66-3q76-h5p5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.