Privasys enclave-os-virtual
enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < tdx-v0.2.43
- < tdx-gpu-v0.6.27
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/Privasys/enclave-os-virtual/securit…
- Patch github.com/Privasys/enclave-os-virtual/commit/…
- Release notes github.com/Privasys/enclave-os-virtual/release…
1 more
- Release notes github.com/Privasys/enclave-os-virtual/release…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.