Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Prior to 0.5.0, the Rust and Go RA-TLS challenge verifiers accepted quote ReportData that was bound to the certificate public key and client nonce but not to the active TLS session before permitting application traffic. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing the clients to accept an attacker-terminated connection as the attested enclave. This issue is fixed in 0.5.0.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-16 20:04
- First seenCVSS 9.1NVD modified 2026-10-13 21:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- https://github.com/Privasys/ra-tls-clients/commit/b8de9bcadd0f81ca8882d15095fc0d9c50e40148
- https://github.com/Privasys/ra-tls-clients/releases/tag/v0.5.0
- https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-5qrc-v874-mxvx
- https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-5qrc-v874-mxvx
- https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-5qrc-v874-mxvx
- https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-5qrc-v874-mxvx
- https://privasys.org/blog/binding-attestation-to-the-tls-session