Truncated packet could crash via OOB read
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 57%. No fixed version is recorded.
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| OpenSSL | OpenSSL | =openssl-1.0.2, =openssl-1.0.2a, =openssl-1.0.2b, =openssl-1.0.2c, =openssl-1.0.2d, =openssl-1.0.2e, =openssl-1.0.2f, =openssl-1.0.2g, =openssl-1.0.2h, =openssl-1.0.2i, =openssl-1.0.2j, =openssl-1.1.0, =openssl-1.1.0a, =openssl-1.1.0b, =openssl-1.1.0c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in OpenSSL, strongest first
Embed
A live severity badge for an advisory, README or ticket