Technical impact
OpenSSL’s QUIC server can retain the state of streams that are rejected by the server if the peer resets those streams before the server has sent a STOP_SENDING frame. Each uncollected rejected stream consumes roughly 300 bytes of memory, and the peer’s stream credit window controls the rate at which these streams accrue. Over a long‑lived connections, an attacker can repeatedly open and reset streams, causing the server’s memory to grow without bound until the process exhausts available memory and all of its connections are lost. The vulnerability is a classic instance of CWE‑401, missing release of memory after effective lifetime, and leads to a DoS condition rather than corruption or disclosure. Doors to exploitation require a persistent QUIC connection, the client must honor the handshake and trigger stream resets, and the server must be running a configuration that rejects streams by default.
Affected Systems
OpenSSL QUIC servers that use the default stream rejection policy or that explicitly configure a REJECT policy. This includes any application built on OpenSSL that implements the QUIC protocol and does not apply the vendor‑provided patch. The advisory does not specify exact version ranges, but any OpenSSL release obtained before the patches referenced in the advisory is vulnerable.
Risk and Exploitability
The vulnerability’s low severity and the slow memory growth path reduce its immediate exploit impact, yet the possibility of exhausting system memory remains. Because memory leaks are not tied to buffer overflows or privilege escalation, the potential for cross‑process or normal user compromise is low, but the target system may experience a denial of service after sustaining a long‑lived QUIC session with many stream resets. The opportunistic nature of the attack and the lack of publicly available exploit code mean that this condition is not highly critical, yet it is significant enough to warrant a patch and monitoring. No known exploitation is present in the KEV catalog.