Descrizione
Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module.
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: CVSS 6.5, EPSS 0.2% (percentile 9).
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/1a73dc590cbad62d6f0329ea4779eadaa8d8fd75
- Riferimentohttps://github.com/openssl/openssl/commit/7b4f5344aa0401e7b777640050b5257ed2a70e88
- Riferimentohttps://github.com/openssl/openssl/commit/911eee8eb7550b95a206f1ad8cbdb986098982f3
- Riferimentohttps://openssl-library.org/news/secadv/20261110.txt