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

> Attackers can bypass TPM attestation by using a software TPM AK after passing EK validation, breaking the chain of trust in Keylime.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jf66-3q76-h5p5, GHSA-jf66-3q76-h5p5,, PYSEC-2022-184, openSUSE-SU-2024:12104-1

## What is CVE-2022-1053?

CVE-2022-1053 is a critical vulnerability in Fedoraproject Fedora, published on 6 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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,

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-1053?

3 open source packages ship an affected version, including keylime. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keylime` | PyPI | All versions | 6.4.0 |
| `keylime` | PyPI | All versions | 6.4.0 |
| `keylime` | PyPI | All versions | 6.4.0 |

Products: Fedoraproject Fedora, Keylime Keylime.

## How do I fix CVE-2022-1053?

Upgrade keylime to 6.4.0 or later.

## Is CVE-2022-1053 being exploited?

There is no known exploitation of CVE-2022-1053 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1053 and fix it if it is affected.

What it is: CVE-2022-1053 is a critical vulnerability in Fedoraproject Fedora, published on 6 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1053 in the wild and no public exploit code.

Affected packages and fixed versions:
- keylime (PyPI): affected all versions; fixed in 6.4.0
- keylime (PyPI): affected all versions; fixed in 6.4.0
- keylime (PyPI): affected all versions; fixed in 6.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1053/ (Markdown: https://insights.sbomify.com/CVE-2022-1053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1053
- OSV: https://osv.dev/vulnerability/CVE-2022-1053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1053/
Summaries are generated and may contain mistakes; the official description above is the record.