Loading vulnerability…
TLS session binding failure in Enclave OS Virtual RA-TLS attestation
Enclave OS Virtual's TDX/GPU RA-TLS certificate issuer, in releases before tdx-v0.2.43 and tdx-gpu-v0.6.27, fails to bind attestation evidence to the active TLS session. The issuer includes the certificate public-key hash and client nonce in quote ReportData but omits a session-bound value. An attacker possessing an enclave TLS private key can relay a genuine quote onto another connection, causing a relying party to accept an attacker-terminated TLS connection as the attested enclave.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation undermines the authenticity of RA-TLS connections: a relying party can accept a connection terminated by an attacker as belonging to an attested enclave. The genuine quote consequently no longer establishes that the active TLS connection terminates inside the enclave.
Patch, then assume compromise.
Upgrade the affected Enclave OS Virtual release line to tdx-v0.2.43 or tdx-gpu-v0.6.27, respectively, which fix the vulnerability.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.