First published: Thu Aug 07 2014(Updated: )
A race condition was found in the ssl_parse_serverhello_tlsext() code that may result in upto 255 bytes being written to memory that had been free'd if an ec point format extension was sent by the server. This issue only affects multi-threaded clients.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openssl | <1.0.1 | 1.0.1 |
OpenSSL libcrypto | =1.0.0 | |
OpenSSL libcrypto | =1.0.0-beta1 | |
OpenSSL libcrypto | =1.0.0-beta2 | |
OpenSSL libcrypto | =1.0.0-beta3 | |
OpenSSL libcrypto | =1.0.0-beta4 | |
OpenSSL libcrypto | =1.0.0-beta5 | |
OpenSSL libcrypto | =1.0.0a | |
OpenSSL libcrypto | =1.0.0b | |
OpenSSL libcrypto | =1.0.0c | |
OpenSSL libcrypto | =1.0.0d | |
OpenSSL libcrypto | =1.0.0e | |
OpenSSL libcrypto | =1.0.0f | |
OpenSSL libcrypto | =1.0.0g | |
OpenSSL libcrypto | =1.0.0h | |
OpenSSL libcrypto | =1.0.0i | |
OpenSSL libcrypto | =1.0.0j | |
OpenSSL libcrypto | =1.0.0k | |
OpenSSL libcrypto | =1.0.0l | |
OpenSSL libcrypto | =1.0.0m | |
OpenSSL libcrypto | =1.0.1 | |
OpenSSL libcrypto | =1.0.1-beta1 | |
OpenSSL libcrypto | =1.0.1-beta2 | |
OpenSSL libcrypto | =1.0.1-beta3 | |
OpenSSL libcrypto | =1.0.1a | |
OpenSSL libcrypto | =1.0.1b | |
OpenSSL libcrypto | =1.0.1c | |
OpenSSL libcrypto | =1.0.1d | |
OpenSSL libcrypto | =1.0.1e | |
OpenSSL libcrypto | =1.0.1f | |
OpenSSL libcrypto | =1.0.1g | |
OpenSSL libcrypto | =1.0.1h |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-3509 is considered a medium severity vulnerability due to its potential for memory corruption in multi-threaded OpenSSL clients.
To fix CVE-2014-3509, upgrade OpenSSL to at least version 1.0.1h or later.
CVE-2014-3509 affects multi-threaded clients using OpenSSL versions 1.0.0 and 1.0.1 prior to 1.0.1h.
CVE-2014-3509 is caused by a race condition in the ssl_parse_serverhello_tlsext() function when handling ec point format extensions.
Yes, CVE-2014-3509 can be exploited to potentially write to freed memory, leading to undefined behavior in affected applications.