tpm2-tss (FAPI quote verification): The JSON quote info returned by Fapi_Quote accepts an arbitrary TPM2_GENERATED

Impact

The JSON quote info returned by Fapi_Quote accepts an arbitrary TPM2_GENERATED magic value, so a malicious device can hand back a quote that the library accepts but that the TPM never produced. That is attestation forgery: a compromised node convinces the verifier it booted a measured, clean image. For any operator selling verified bare metal or confidential GPU compute, this breaks the assertion the whole product rests on - and it breaks it silently, since a forged quote validates.

Who can reach it

A malicious or compromised endpoint being attested. The attacker is the machine claiming to be healthy, not a third party on the wire.

What to do

Update tpm2-tss to 4.1.0 or later wherever your attestation verifier runs and restart the service - package-level, no firmware, no reboot. Then re-run attestation across the fleet, because any quote validated by the old library proves nothing. Worth auditing whether your verifier does its own magic-value check rather than trusting the library.

References