First published: Thu Apr 28 2016(Updated: )
It was discovered that OpenSSL leaked timing information when decrypting TLS/SSL and DTLS protocol encrypted records when the connection used the AES CBC cipher suite and the server supported AES-NI. A remote attacker could possibly use this flaw to retrieve plain text from encrypted packets by using a TLS/SSL or DTLS server as a padding oracle.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openssl | <1.0.1 | 1.0.1 |
redhat/openssl | <1.0.2 | 1.0.2 |
redhat/openssl | <0:1.0.1e-48.el6_8.1 | 0:1.0.1e-48.el6_8.1 |
redhat/openssl | <0:1.0.1e-42.el6_7.5 | 0:1.0.1e-42.el6_7.5 |
redhat/openssl | <1:1.0.1e-51.el7_2.5 | 1:1.0.1e-51.el7_2.5 |
redhat enterprise Linux desktop | =7.0 | |
Red Hat Enterprise Linux HPC Node | =7.0 | |
Red Hat Enterprise Linux HPC Node | =7.2 | |
redhat enterprise Linux server | =7.0 | |
redhat enterprise Linux server aus | =7.2 | |
redhat enterprise Linux server eus | =7.2 | |
redhat enterprise Linux workstation | =7.0 | |
openSUSE | =42.1 | |
openSUSE | =13.2 | |
OpenSSL libcrypto | <=1.0.1s | |
OpenSSL libcrypto | =1.0.2 | |
OpenSSL libcrypto | =1.0.2-beta1 | |
OpenSSL libcrypto | =1.0.2-beta2 | |
OpenSSL libcrypto | =1.0.2-beta3 | |
OpenSSL libcrypto | =1.0.2a | |
OpenSSL libcrypto | =1.0.2b | |
OpenSSL libcrypto | =1.0.2c | |
OpenSSL libcrypto | =1.0.2d | |
OpenSSL libcrypto | =1.0.2e | |
OpenSSL libcrypto | =1.0.2f | |
OpenSSL libcrypto | =1.0.2g | |
Android | =4.0 | |
Android | =4.0.1 | |
Android | =4.0.2 | |
Android | =4.0.3 | |
Android | =4.0.4 | |
Android | =4.1 | |
Android | =4.1.2 | |
Android | =4.2 | |
Android | =4.2.1 | |
Android | =4.2.2 | |
Android | =4.3 | |
Android | =4.3.1 | |
Android | =4.4 | |
Android | =4.4.1 | |
Android | =4.4.2 | |
Android | =4.4.3 | |
Android | =5.0 | |
Android | =5.0.1 | |
Android | =5.1 | |
Android | =5.1.0 | |
HP Helion OpenStack | =2.0 | |
HP Helion OpenStack | =2.1 | |
HP Helion OpenStack | =2.1.2 | |
HP Helion OpenStack | =2.1.4 | |
redhat enterprise Linux desktop | =6.0 | |
Red Hat Enterprise Linux HPC Node | =6.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux workstation | =6.0 | |
Node.js | >=0.10.0<0.10.45 | |
Node.js | >=0.12.0<0.12.14 | |
Node.js | >=4.0.0<=4.1.2 | |
Node.js | >=4.2.0<4.4.4 | |
Node.js | >=5.0.0<5.11.1 | |
Node.js | =6.0.0 | |
Debian | =8.0 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =15.10 | |
Ubuntu | =16.04 | |
HP Helion OpenStack | =2.0.0 | |
HP Helion OpenStack | =2.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2016-2107 is classified as a medium severity vulnerability that allows potential information disclosure through timing attacks.
To remediate CVE-2016-2107, users must upgrade to OpenSSL version 1.0.1s or later, or 1.0.2 or later, depending on their specific installation.
CVE-2016-2107 affects OpenSSL versions 1.0.1 through 1.0.1r and 1.0.2 through 1.0.2g.
Yes, CVE-2016-2107 can be exploited by a remote attacker to retrieve plaintext from encrypted packets.
The potential impacts of CVE-2016-2107 include unauthorized access to sensitive information through the exploitation of a timing attack.