Non notée
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…
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,
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| keylime | Versions non publiées |
Références
- github.com github.com
- bugzilla.redhat.com bugzilla.redhat.com
- github.com github.com
- FEDORA-2022-748fda10e7 lists.fedoraproject.org
- FEDORA-2022-7c9173843a lists.fedoraproject.org
- FEDORA-2022-f9ace23a78 lists.fedoraproject.org
Chronologie
- Publiée
- Dernière modification
Autres CVE de keylime
Les 9 CVE de keylime →
CVE-2022-3500
A vulnerability was found in keylime
5.1
Moyenne
CVE-2022-23952
In Keylime before 6.3.0, current keylime installer installs the keylime.conf file, which can contain sensitive data,…
7.5
Élevée
CVE-2022-23951
In Keylime before 6.3.0, quote responses from the agent can contain possibly untrusted ZIP data which can lead to zip…
5.5
Moyenne
CVE-2022-23950
In Keylime before 6.3.0, Revocation Notifier uses a fixed /tmp path for UNIX domain socket which can allow…
7.5
Élevée