CVE Intelligence

Vulnerabilidades do Go standard library Crypto/tls

🔔 Criar alerta RSS Verificador de versão

CVEs publicadas que afetam Go standard library Crypto/tls: 7 registro(s), com versões afetadas e correções.

CVE-2026-97031 Alta · 7.5 CWE-405 08/10/2026
Reject malformed ECH outer extension references in crypto/tls
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
CVE-2026-56862 Alta · 7.5 CWE-770 13/08/2026
Limit handshake messages we are willing to accept post-handshake in crypto/tls
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
CVE-2026-42505 Média · 5.3 CWE-201 08/07/2026
Invoking Encrypted Client Hello privacy leak in crypto/tls
Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello.
CVE-2026-32283 Alta · 7.5 CWE-770 07/04/2026
Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
CVE-2025-68121 Crítica · 10.0 CWE-295 05/02/2026
Falha de validação de certificado na retomada de sessão do crypto/tls do Go
Durante a retomada de sessão em crypto/tls, se a Config subjacente tiver os campos ClientCAs ou RootCAs alterados entre o handshake inicial e o handshake retomado, o handshake retomado pode ser bem-sucedido quando deveria ter falhado. Isso pode ocorrer quando um usuário chama Config.Clone e altera a Config retornada, ou usa Config.GetConfigForClient. Isso pode fazer com que um cliente retome uma sessão com um servidor com o qual não retomaria durante o handshake inicial, ou fazer com que um servidor retome uma sessão com um cliente com o qual não retomaria durante o handshake inicial.
CVE-2025-61730 Média · 5.3 28/01/2026
Handshake messages may be processed at the incorrect encryption level in crypto/tls
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
CVE-2025-58189 Média · 5.3 CWE-532 29/10/2025
ALPN negotiation error contains attacker controlled information in crypto/tls
When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped.