CVE-2022-1053

描述

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,

如何修補 CVE-2022-1053

要修補 CVE-2022-1053,請將受影響套件升級到下列已修補版本。

• —升級至 6.4.0 或更新版本
• —升級至 bd5de712acdd77860e7dc58969181e16c7a8dc5d 或更新版本

CVE-2022-1053 正在被利用嗎?

低 — EPSS 為 1.3%,目前沒有觀察到大規模利用活動。

受影響套件(2)

• from 0, < 6.4.0
• from 0, < bd5de712acdd77860e7dc58969181e16c7a8dc5d | from 0, < 6.4.0

CVSS 分數

參考連結(15)

• ADVISORYgithub.com/advisories/GHSA-jf66-3q76-h5p5
• ADVISORYgithub.com/keylime/keylime/security/advisories/GHSA-jf66-3q76-h5p5,
• ADVISORYnvd.nist.gov/vuln/detail/CVE-2022-1053
• PATCHgithub.com/keylime/keylime
• REPORT