Bug 2065024 (CVE-2022-1053) - CVE-2022-1053 keylime: Tenant and Verifier might not use the same registrar data
Summary: CVE-2022-1053 keylime: Tenant and Verifier might not use the same registrar data
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-1053
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2082162
Blocks: 2082413
TreeView+ depends on / blocked
 
Reported: 2022-03-17 06:57 UTC by TEJ RATHI
Modified: 2022-09-20 10:32 UTC (History)
6 users (show)

Fixed In Version: keylime 6.4.0
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2022-05-05 18:15:20 UTC
Embargoed:


Attachments (Terms of Use)

Description TEJ RATHI 2022-03-17 06:57:14 UTC
Hello Team, please check the below report:
--------

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.

Affects all versions of Keylime <6.4.0

Thanks

Comment 7 Avinash Hanwate 2022-05-05 14:00:02 UTC
lifting embargo as it is public now.
Ref: https://github.com/keylime/keylime/security/advisories/GHSA-jf66-3q76-h5p5

Comment 8 Avinash Hanwate 2022-05-05 14:00:21 UTC
Created keylime tracking bugs for this issue:

Affects: fedora-all [bug 2082162]

Comment 9 Product Security DevOps Team 2022-05-05 18:15:18 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.