TPM-protected data disclosure via omitted PCR checks
Published Feb 26, 2021 · Updated Aug 4, 2024
Missing initialization in tpm2-tss before 2.4.3 and 3.0.0 allows local users with high privileges to read TPM-protected data. When currentPcrs or currentPcrsAndBank instantiates a PolicyPCR, an uninitialized variable causes the generated policy to omit PCR checks. High-privileged local access is required, and objects created under the faulty policy lack the intended PCR-state restriction.
Summary
What happened
Missing initialization in tpm2-tss before 2.4.3 and 3.0.0 allows local users with high privileges to read TPM-protected data. When currentPcrs or currentPcrsAndBank instantiates a PolicyPCR, an uninitialized variable causes the generated policy to omit PCR checks. High-privileged local access is required, and objects created under the faulty policy lack the intended PCR-state restriction.
The record
- CVE
- CVE-2020-24455
- Published
- Feb 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- TPM2 Software
- Product
- TPM2 Software Stack (tpm2-tss)
- Classifications
- CWE-909, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 3.01, before 2.4.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo