Marten Seemann

**Name of the Vulnerable Software and Affected Versions** QUIC (affected versions not specified) **Description** The issue allows a malicious QUIC connection to cause unbounded memory growth due to the lack of an upper bound on the amount of data buffered when reading post-handshake messages. With the fix applied, connections now consistently reject messages larger than 65KiB in size. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Go (affected versions not specified) **Description** The issue is related to the processing of incomplete post-handshake messages for QUIC connections, which can cause a panic. Additionally, there is a vulnerability in the HandleData() function of the crypto/tls package in the Go programming language, associated with incorrect data volume limitation before buffering. This vulnerability can be exploited by a remote attacker to cause a denial of service. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** crypto/tls versions prior to the fixed version **Description** The issue is related to large handshake records that may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records, which can cause servers and clients to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients that explicitly enable session resumption by setting `Config.ClientSessionCache` to a non-nil value, and TLS 1.3 servers that request client certificates by setting `Config.ClientAuth` to a value greater than or equal to `RequestClientCert`. **Recommendations** As a temporary workaround, consider disabling the `Config.ClientSessionCache` for TLS 1.2 clients and restricting the use of `Config.ClientAuth` for TLS 1.3 servers until a patch is available. For TLS 1.3 clients, consider implementing a handshake record size limit to prevent large records from being sent. For TLS 1.2 clients with session resumption enabled, consider disabling session resumption until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.