First published: Thu Aug 07 2014(Updated: )
By pathologically modifying a clients ClientHello message with fragmentation, it's possible to cause the server to negotiate TLS 1.0 instead of a higher version, even if both client and server support a higher protocol version.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openssl | <1.0.1 | 1.0.1 |
OpenSSL OpenSSL | =1.0.0 | |
OpenSSL OpenSSL | =1.0.0-beta1 | |
OpenSSL OpenSSL | =1.0.0-beta2 | |
OpenSSL OpenSSL | =1.0.0-beta3 | |
OpenSSL OpenSSL | =1.0.0-beta4 | |
OpenSSL OpenSSL | =1.0.0-beta5 | |
OpenSSL OpenSSL | =1.0.0a | |
OpenSSL OpenSSL | =1.0.0b | |
OpenSSL OpenSSL | =1.0.0c | |
OpenSSL OpenSSL | =1.0.0d | |
OpenSSL OpenSSL | =1.0.0e | |
OpenSSL OpenSSL | =1.0.0f | |
OpenSSL OpenSSL | =1.0.0g | |
OpenSSL OpenSSL | =1.0.0h | |
OpenSSL OpenSSL | =1.0.0i | |
OpenSSL OpenSSL | =1.0.0j | |
OpenSSL OpenSSL | =1.0.0k | |
OpenSSL OpenSSL | =1.0.0l | |
OpenSSL OpenSSL | =1.0.0m | |
OpenSSL OpenSSL | =1.0.1 | |
OpenSSL OpenSSL | =1.0.1-beta1 | |
OpenSSL OpenSSL | =1.0.1-beta2 | |
OpenSSL OpenSSL | =1.0.1-beta3 | |
OpenSSL OpenSSL | =1.0.1a | |
OpenSSL OpenSSL | =1.0.1b | |
OpenSSL OpenSSL | =1.0.1c | |
OpenSSL OpenSSL | =1.0.1d | |
OpenSSL OpenSSL | =1.0.1e | |
OpenSSL OpenSSL | =1.0.1f | |
OpenSSL OpenSSL | =1.0.1g | |
OpenSSL OpenSSL | =1.0.1h |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.