enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session
Privasys enclave-os-virtual
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Privasys enclave-os-virtual |
| No fix yet |
Original description
Enclave OS Virtual runs container workloads inside confidential virtual machines with end-to-end attestation. Prior to tdx-v0.2.43 and tdx-gpu-v0.6.27, the TDX/GPU RA-TLS certificate issuer placed the certificate public-key hash and client nonce in quote ReportData but omitted a value bound to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept an attacker-terminated connection as the attested enclave. This issue is fixed in tdx-v0.2.43 and tdx-gpu-v0.6.27.
From the CVE record · GitHub_M