Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Privasys | rustls | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Privasys | Rustls |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.117% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Privasys
Privasys rustls |
|
| Vendors & Products |
Privasys
Privasys rustls |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Privasys rustls is a maintained fork of the rustls TLS library that adds RA-TLS challenge and channel-binding support. Prior to privasys-v0.8.1, the fork emitted RA-TLS challenge certificates whose quote ReportData was bound to the certificate public key and client nonce but not 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 privasys-v0.8.1. | |
| Title | Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session | |
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
cvssV4_0
|