# CVE-2024-29039: Missing check in tpm2_checkquote allows attackers to misrepresent the TPM state

> Attackers can manipulate TPM state verification by altering PCR inputs, leading to misleading digest mappings and potential security bypasses.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jun 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-43015, AZL-43021, CLSA-2025-1764614196, DEBIAN-CVE-2024-29039, GHSA-8rjm-5f5f-h4q6, UBUNTU-CVE-2024-29039

## What is CVE-2024-29039?

CVE-2024-29039 is a critical vulnerability in tpm2-software tpm2-tools, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tpm2 is the source repository for the Trusted Platform Module (TPM2.0) tools. This vulnerability allows attackers to manipulate tpm2_checkquote outputs by altering the TPML_PCR_SELECTION in the PCR input file.  As a result, digest values are incorrectly mapped to PCR slots and banks, providing a misleading picture of the TPM state. This issue has been patched in version 5.7.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

## Which versions are affected by CVE-2024-29039?

It affects 1 product.


Products: Tpm2-Tools Project Tpm2-Tools.

## How do I fix CVE-2024-29039?

Upgrade to a fixed version.

## Is CVE-2024-29039 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29039 exists.

## Other vulnerabilities in tpm2-software tpm2-tools

- [CVE-2024-29038](https://insights.sbomify.com/CVE-2024-29038/): tpm2 does not detect if quote was not generated by TPM (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29039 and fix it if it is affected.

What it is: CVE-2024-29039 is a critical vulnerability in tpm2-software tpm2-tools, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29039 exists.

Affected product: tpm2-software tpm2-tools. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-29039/ (Markdown: https://insights.sbomify.com/CVE-2024-29039/index.md)
```

## Sources

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

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