# CVE-2022-1053: Tenant and Verifier might not use the same registrar data

Source: https://junglewise.ai/threats/cve-2022-1053-tenant-and-verifier-might-not-use-the-same-registrar-data  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-05-06  
License: CC BY 4.0 with a link back

CVE-2022-1053 · Severity: low · CVSS 3.1 · Published 2022-05-06

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,

Technologies: [keylime (PyPI)](https://junglewise.ai/threats/technologies/keylime). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2022-1053 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-1053 being exploited in the wild.

**How severe is CVE-2022-1053?** Low severity, with a CVSS score of 3.1, published 6 May 2022.

**Which products and versions are affected?** keylime (PyPI) ECOSYSTEM:introduced=0,fixed=6.4.0, GIT:introduced=0,fixed=bd5de712acdd77860e7dc58969181e16c7a8dc5d|ECOSYSTEM:introduced=0,fixed=6.4.0.

**Is there a fix for CVE-2022-1053?** Yes. keylime (PyPI): upgrade to 6.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2022-1053?** Check whether you run keylime (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- keylime (PyPI): upgrade to 6.4.0 or later

  ```sh
  pip install "keylime>=6.4.0"
  ```


## Affected products

- keylime (PyPI) ECOSYSTEM:introduced=0,fixed=6.4.0, GIT:introduced=0,fixed=bd5de712acdd77860e7dc58969181e16c7a8dc5d|ECOSYSTEM:introduced=0,fixed=6.4.0

## Identifiers

- CVE-2022-1053
- GHSA-jf66-3q76-h5p5
- PYSEC-2022-184

## Related threats

- [PYSEC-2026-1489 - Keylime's registrar vulnerable to Denial-of-service attack via a single open connection](https://junglewise.ai/threats/cve-2023-38200-keylime-s-registrar-vulnerable-to-denial-of-service-attack-via-a)
- [Keylime security bypass via hardcoded TPM attestation nonce](https://junglewise.ai/threats/keylime-security-bypass-via-hardcoded-tpm-attestation-nonce-16dcb84a)
- [Keylime security bypass via hardcoded TPM quote nonce](https://junglewise.ai/threats/cve-2026-6420-keylime-security-bypass-via-hardcoded-tpm-quote-nonce)
- [Keylime registrar authentication bypass via missing TLS validation](https://junglewise.ai/threats/keylime-registrar-authentication-bypass-via-missing-tls-validation-f26498d5)
- [Keylime authentication bypass in registrar component](https://junglewise.ai/threats/cve-2026-1709-keylime-authentication-bypass-in-registrar-component)
