Memory exhaustion in QUIC connection handling in crypto/tls
QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth.
container-tools:4.0 security update
Released 2024-01-10 · Red Hat rating Moderate · View on Red Hat →
QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth.
Processing an incomplete post-handshake message for a QUIC connection can cause a panic.
In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error.
Reader.Read does not set a limit on the maximum size of file headers.
Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.
Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http.
The html/template package does not apply the proper rules for handling occurrences of "<script", "<!--", and "</script" within JS literals in <script> contexts.
The html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in <script> contexts.
Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures.