Privasys attested TLS accepted evidence from any unrevoked TEE platform (diversion attack)
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 | ra-tls-clients | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Privasys | Ra-tls-clients |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.159% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Privasys
Privasys ra-tls-clients |
|
| Vendors & Products |
Privasys
Privasys ra-tls-clients |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Prior to 0.11.0, TEE attestation evidence in Privasys attested TLS is accepted without requiring an explicitly authorized platform identity. When a network attacker can forge evidence or extract attestation secrets from a compromised unrevoked platform, the verifier accepts valid measurements from a different unrevoked TEE platform as though they came from the intended Attester. The attacker can impersonate the attested TLS endpoint. This issue is fixed in version 0.11.0. | |
| Title | Privasys attested TLS accepted evidence from any unrevoked TEE platform (diversion attack) | |
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
cvssV4_0
|