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,
Advisories
Source ID Title
EUVD EUVD EUVD-2022-0134 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,
Github GHSA Github GHSA GHSA-jf66-3q76-h5p5 Tenant and Verifier might not use the same registrar data
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2024-08-02T23:47:43.276Z

Reserved: 2022-03-22T00:00:00

Link: CVE-2022-1053

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2022-05-06T17:15:08.770

Modified: 2024-11-21T06:39:56.393

Link: CVE-2022-1053

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.