# CVE-2024-29038: tpm2 does not detect if quote was not generated by TPM

> Attackers can forge TPM quote data that bypasses verification in tpm2-tools, undermining integrity checks for trusted platform modules.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jun 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-43018, CLSA-2026-1782977868, DEBIAN-CVE-2024-29038, GHSA-5495-c38w-gr6f, UBUNTU-CVE-2024-29038

## What is CVE-2024-29038?

CVE-2024-29038 is a medium-severity vulnerability in tpm2-software tpm2-tools, published on 28 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

tpm2-tools is the source repository for the Trusted Platform Module (TPM2.0) tools. A malicious attacker can generate arbitrary quote data which is not detected by `tpm2 checkquote`. This issue was patched in version 5.7.

Weakness: CWE-1390 (Weak Authentication), CWE-1283 (Mutable Attestation or Measurement Reporting Data)

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

It affects 1 product.


Products: Tpm2-Tools Project Tpm2-Tools.

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

Upgrade to a fixed version.

## Is CVE-2024-29038 being exploited?

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

## Other vulnerabilities in tpm2-software tpm2-tools

- [CVE-2024-29039](https://insights.sbomify.com/CVE-2024-29039/): Missing check in tpm2_checkquote allows attackers to misrepresent the TPM state (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29038 is a medium-severity vulnerability in tpm2-software tpm2-tools, published on 28 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29038 in the wild and no public exploit code.

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

## Sources

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

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