Descrizione
Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 7.5, EPSS 0.6% (percentile 48).
Versioni da aggiornare
- OpenSSL OpenSSL: vulnerabili le versioni dalla
4.1.0precedenti alla4.1.1→ aggiornare alla4.1.1o successiva. - OpenSSL OpenSSL: vulnerabili le versioni dalla
4.0.0precedenti alla4.0.4→ aggiornare alla4.0.4o successiva. - OpenSSL OpenSSL: vulnerabili le versioni dalla
3.5.0precedenti alla3.5.10→ aggiornare alla3.5.10o successiva.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| OpenSSL | OpenSSL | ≥ 4.1.0 < 4.1.1 | 4.1.1 |
| OpenSSL | OpenSSL | ≥ 4.0.0 < 4.0.4 | 4.0.4 |
| OpenSSL | OpenSSL | ≥ 3.5.0 < 3.5.10 | 3.5.10 |
Riferimenti
- Riferimentohttps://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2
- Riferimentohttps://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7
- Riferimentohttps://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05
- Riferimentohttps://openssl-library.org/news/secadv/20261117.txt