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,
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| — | keylime | Affects keylime v6.4.0 and prior, Fixed in – v6.4.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP4 | keylime | 6.3.2-150400.4.11.1 | SUSE-SU-2022:2658-1 |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 15.4 | keylime | 6.3.2-150400.4.11.1 | SUSE-SU-2022:2658-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | keylime | < 6.4.0 | 6.4.0 | GHSA-jf66-3q76-h5p5 |
Advisories 1
- SUSE-SU-2022:2658-1 Security update for keylime SUSE / openSUSE Security Updates · Feb 4, 2026
References
- https://github.com/keylime/keylime/commit/bd5de712acdd77860e7dc58969181e16c7a8dc5d
- https://bugzilla.redhat.com/show_bug.cgi?id=2065024%2C
- https://github.com/keylime/keylime/security/advisories/GHSA-jf66-3q76-h5p5%2C
- FEDORA-2022-748fda10e7 vendor-advisory
- FEDORA-2022-7c9173843a vendor-advisory
- FEDORA-2022-f9ace23a78 vendor-advisory