Vulnerabilidades de Privasys
CVEs publicadas que afetam produtos de Privasys: 7 registro(s), com severidade, exploração e correções.
CVE-2026-108362
Crítica · 9.1
CWE-346 12/10/2026
Privasys Remote Attestation TLS Clients: TLS attestado aceita evidência de plataforma TEE não autorizada (CWE-346)
O Privasys Remote Attestation TLS Clients fornece utilitários em múltiplas linguagens para verificar conexões TLS atestadas. Antes da versão 0.11.0, as evidências de atestação TEE no Privasys attested TLS são aceitas sem exigir uma identidade de plataforma explicitamente autorizada. Quando um atacante de rede consegue forjar evidências ou extrair segredos de atestação de uma plataforma comprometida e não revogada, o verificador aceita medições válidas de uma plataforma TEE diferente e não revogada como se tivessem vindo do Attester pretendido. O atacante pode se passar pelo endpoint TLS atestado. Este problema foi corrigido na versão 0.11.0.
CVE-2026-108361
Alta · 7.2
CWE-367 12/10/2026
Privasys Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks
Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Before 0.9.1, an attacker with local access could modify workload code, data, and configuration at any time after successful connection establishment. Once Evidence was successfully appraised and the connection was established, there was a window of vulnerability from the establishment of the connection to the termination of the connection where an attacker could modify the state of the workload and platform at runtime on the TLS endpoint acting as the Attester. This vulnerability was possible because Privasys/ra-tls-clients performed attestation only once in the lifetime of the connection (at connection establishment time), and the verifying peer continued to believe that the state was the same as in the initial Evidence throughout, whereas it could be stale at some point in time. This vulnerability is fixed in 0.9.1.
CVE-2026-108267
Crítica · 9.1
CWE-346 09/10/2026
Falha de vinculação da atestação à sessão TLS no Privasys Go RA-TLS
Privasys Go é um fork mantido da linguagem de programação Go que adiciona suporte a RA-TLS ao crypto/tls. Antes de privasys-v0.5.1-go1.26.5, certificados RA-TLS em modo challenge vinculavam o ReportData da quote à chave pública do certificado e ao nonce do cliente, mas não à sessão TLS ativa. Um atacante que obtivesse a chave privada TLS de um enclave poderia retransmitir uma quote genuína para outra conexão, levando uma parte confiável a aceitar um handshake encerrado pelo atacante como uma conexão de enclave atestada. Este problema está corrigido em privasys-v0.5.1-go1.26.5.
CVE-2026-108269
Crítica · 9.1
CWE-346 09/10/2026
ra-tls-clients: RA-TLS challenge verifier accepted quotes not bound to the TLS session
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.
CVE-2026-108268
Crítica · 9.1
CWE-346 09/10/2026
enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session
Enclave OS Virtual runs container workloads inside confidential virtual machines with end-to-end attestation. Prior to tdx-v0.2.43 and tdx-gpu-v0.6.27, the TDX/GPU RA-TLS certificate issuer placed the certificate public-key hash and client nonce in quote ReportData but omitted a value bound 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 tdx-v0.2.43 and tdx-gpu-v0.6.27.
CVE-2026-108266
Crítica · 9.1
CWE-346 09/10/2026
Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session
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.
CVE-2026-108265
Crítica · 9.1
CWE-346 09/10/2026
enclave-os-mini: RA-TLS challenge certificates were not bound to the TLS session
Enclave OS Mini is a Rust-based runtime for confidential applications inside Intel SGX enclaves. Prior to wasm-v0.40.0, the SGX runtime's RA-TLS challenge certificate path placed the certificate public-key hash and client nonce in quote ReportData but omitted a value bound 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 wasm-v0.40.0.