Descrizione
Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary.
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: CVSS 5.3, EPSS 0.3% (percentile 20).
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. - OpenSSL OpenSSL: vulnerabili le versioni dalla
3.0.0precedenti alla3.0.24→ aggiornare alla3.0.24o successiva. - OpenSSL OpenSSL: vulnerabili le versioni dalla
1.1.1precedenti alla1.1.1zk→ aggiornare alla1.1.1zko successiva. - OpenSSL OpenSSL: vulnerabili le versioni dalla
1.0.2precedenti alla1.0.2zt→ aggiornare alla1.0.2zto successiva.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Applicare rate limiting e limiti sulle risorse a monte del servizio e monitorarne la disponibilità.
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 |
| OpenSSL | OpenSSL | ≥ 3.0.0 < 3.0.24 | 3.0.24 |
| OpenSSL | OpenSSL | ≥ 1.1.1 < 1.1.1zk | 1.1.1zk |
| OpenSSL | OpenSSL | ≥ 1.0.2 < 1.0.2zt | 1.0.2zt |
Riferimenti
- Riferimentohttps://github.com/openssl/openssl/pull/33620
- Riferimentohttps://github.com/openssl/openssl/pull/33729