An information leakage vulnerability in Trusted Computing Group TPM 2.0 reference code allows privileged local attackers to falsify cryptographic attestations, posing a significant risk to system integrity.

This vulnerability, categorized under CWE-704, stems from incorrect type conversion within the reference code. A local attacker with high privileges can exploit this flaw to obtain unauthorized credentials and forge TPM-based attestations, such as DevID or TLS keys.

The ability to falsify TPM attestations undermines the foundational trust model of the affected hardware. Successful exploitation could lead to unauthorized network access, identity impersonation, and the compromise of secure boot chains. With a CVSS score of 7.9, this high-severity flaw represents a significant risk to environments relying on hardware-backed security for authentication and device integrity.

Immediate Action: Organizations should review the official Trusted Computing Group guidance and errata documents and apply the recommended firmware or library updates as soon as they are made available by hardware vendors.

Proactive Monitoring: Security teams should monitor for anomalous requests to Certificate Authorities (CAs) that involve TPM-based key registrations or unexpected attestation traffic.

Compensating Controls: Implement strict access control lists for local administrative accounts to limit the potential pool of attackers capable of executing privileged commands.

Public Exploit Available: Unknown

This vulnerability represents a critical failure in the cryptographic assurance provided by the TPM 2.0 reference implementation. Administrators must prioritize the identification of affected hardware within their infrastructure and coordinate with OEMs to deploy necessary firmware patches once released. Failure to remediate could allow attackers to bypass hardware-level security controls, effectively neutralizing the protection provided by the TPM.