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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
privasys:ra-tls-clients
References 4
https://github.com/Privasys/ra-tls-clients/commit/b8de9bcadd0f81ca8882d15095fc0…
security-advisories@github.com
https://github.com/Privasys/ra-tls-clients/releases/tag/v0.5.0
security-advisories@github.com
https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-5qrc-v874-m…
security-advisories@github.com
https://privasys.org/blog/binding-attestation-to-the-tls-session
security-advisories@github.com