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. With fix, connections now consistently reject messages larger than 65KiB in size.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-39322US | high7.5 | — | ||
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 growt… | ||||
02
references
External citations — patches, advisories, analysis.
- https://go.dev/cl/523039FIX
- https://go.dev/issue/62266REPORT
- https://groups.google.com/g/golang-dev/c/2C5vbR-UNkI/m/L1hdrPhfBAAJDISCUSSION
- https://nvd.nist.gov/vuln/detail/CVE-2023-39322WEB
- https://pkg.go.dev/vuln/GO-2023-2045ADVISORY
- https://security.gentoo.org/glsa/202311-09WEB
- https://security.netapp.com/advisory/ntap-20231020-0004/ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan