First published: Fri Jan 06 2012(Updated: )
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
OpenSSL libcrypto | =0.9.8b | |
OpenSSL libcrypto | =0.9.7l | |
OpenSSL libcrypto | =0.9.6i | |
OpenSSL libcrypto | =0.9.8m | |
OpenSSL libcrypto | =0.9.8c | |
OpenSSL libcrypto | =0.9.7c | |
OpenSSL libcrypto | =0.9.8n | |
OpenSSL libcrypto | =0.9.8p | |
OpenSSL libcrypto | =0.9.6d | |
OpenSSL libcrypto | =0.9.1c | |
OpenSSL libcrypto | =0.9.6 | |
OpenSSL libcrypto | =0.9.7j | |
OpenSSL libcrypto | =0.9.6a | |
OpenSSL libcrypto | =0.9.8e | |
OpenSSL libcrypto | =0.9.6h-bogus | |
OpenSSL libcrypto | =0.9.4 | |
OpenSSL libcrypto | =0.9.8g | |
OpenSSL libcrypto | =0.9.8k | |
OpenSSL libcrypto | =0.9.8d | |
OpenSSL libcrypto | =0.9.5a | |
OpenSSL libcrypto | =0.9.6f | |
OpenSSL libcrypto | =0.9.8j | |
OpenSSL libcrypto | =0.9.6l | |
OpenSSL libcrypto | =0.9.7k | |
OpenSSL libcrypto | =0.9.7g | |
OpenSSL libcrypto | <=0.9.8r | |
OpenSSL libcrypto | =0.9.6e | |
OpenSSL libcrypto | =0.9.7d | |
OpenSSL libcrypto | =0.9.8l | |
OpenSSL libcrypto | =0.9.7 | |
OpenSSL libcrypto | =0.9.6b | |
OpenSSL libcrypto | =0.9.7e | |
OpenSSL libcrypto | =0.9.7b | |
OpenSSL libcrypto | =0.9.6k | |
OpenSSL libcrypto | =0.9.8a | |
OpenSSL libcrypto | =0.9.6g | |
OpenSSL libcrypto | =0.9.7m | |
OpenSSL libcrypto | =0.9.6h | |
OpenSSL libcrypto | =0.9.7i | |
OpenSSL libcrypto | =0.9.7h | |
OpenSSL libcrypto | =0.9.8o | |
OpenSSL libcrypto | =0.9.8q | |
OpenSSL libcrypto | =0.9.6j | |
OpenSSL libcrypto | =0.9.8 | |
OpenSSL libcrypto | =0.9.7a | |
OpenSSL libcrypto | =0.9.6c | |
OpenSSL libcrypto | =0.9.6m | |
OpenSSL libcrypto | =0.9.8i | |
OpenSSL libcrypto | =0.9.8f | |
OpenSSL libcrypto | =0.9.8h | |
OpenSSL libcrypto | =0.9.2b | |
OpenSSL libcrypto | =0.9.5 | |
OpenSSL libcrypto | =0.9.7f | |
OpenSSL libcrypto | =1.0.0c | |
OpenSSL libcrypto | =1.0.0-beta1 | |
OpenSSL libcrypto | =1.0.0-beta2 | |
OpenSSL libcrypto | =1.0.0-beta3 | |
OpenSSL libcrypto | =1.0.0d | |
OpenSSL libcrypto | <=1.0.0e | |
OpenSSL libcrypto | =1.0.0-beta4 | |
OpenSSL libcrypto | =1.0.0 | |
OpenSSL libcrypto | =1.0.0-beta5 | |
OpenSSL libcrypto | =1.0.0a | |
OpenSSL libcrypto | =1.0.0b |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-4576 has been rated as a moderate severity vulnerability due to the potential for sensitive information disclosure.
To fix CVE-2011-4576, upgrade to a version of OpenSSL that is not affected, specifically version 0.9.8s or later or 1.0.0f or later.
CVE-2011-4576 affects OpenSSL versions from 0.9.1c to 0.9.8r and 1.0.0-beta1 to 1.0.0e.
Yes, exploiting CVE-2011-4576 can allow remote attackers to gain access to sensitive information by decrypting padding data.
As of now, CVE-2011-4576 is a risk if legacy versions of OpenSSL are still in use, especially in sensitive applications.