The flaw allows an attacker who gains the enclave TLS private key to replay a valid attestation quote on a different TLS session. Because the RA-TLS challenge verifier did not tie the quote's ReportData to the active TLS session, the client incorrectly accepted the relayed quote and established application traffic with an untrusted connection. This effectively allows the attacker to masquerade as the protected enclave, potentially enabling remote code execution or unauthorized data access. The weakness maps to CWE-346, which concerns missing or incorrect cryptographic security checks.

Systems using Privasys ra-tls-clients any release prior to 0.5.0 are affected. These include Rust and Go clients that perform the RA-TLS challenge verification without session binding. The product is provided by Privasys and the vulnerability exists in all implementations before the 0.5.0 release.

The CVSS score of 9.1 categorizes this vulnerability as critical. Although EPSS is not available, the lack of a KEV listing does not reduce the risk; the high severity and the nature of the flaw suggest a high likelihood of exploitation if an attacker can access an enclave private key. The attack requires the adversary to obtain the TLS private key and relay a quote; no further privileges are needed beyond that. Mitigation requires upgrading the client to at least 0.5.0, which adds proper TLS session binding.