First published: Mon Jan 05 2015(Updated: )
Multiple flaws were found in the way OpenSSL parsed X.509 certificates. An attacker could use these flaws to modify an X.509 certificate to produce a certificate with a different fingerprint without invalidating its signature, and possibly bypass fingerprint-based blacklisting in applications.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/OpenSSL | <1.0.1 | 1.0.1 |
redhat/OpenSSL | <0.9.8 | 0.9.8 |
redhat/openssl | <0:0.9.8e-33.el5_11 | 0:0.9.8e-33.el5_11 |
redhat/openssl | <0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
redhat/openssl | <1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
OpenSSL libcrypto | <=0.9.8zc | |
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.0n | |
OpenSSL libcrypto | =1.0.0o | |
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 | |
OpenSSL libcrypto | =1.0.1i | |
OpenSSL libcrypto | =1.0.1j |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-8275 has a moderate severity level as it allows attackers to bypass fingerprint-based blacklisting through forged X.509 certificates.
To fix CVE-2014-8275, you should upgrade OpenSSL to versions 1.0.1 or higher beyond 1.0.1h, or install patched versions from the relevant vendor.
CVE-2014-8275 affects multiple versions of OpenSSL, specifically versions 0.9.8 and 1.0.1 up to 1.0.1h.
CVE-2014-8275 can enable attackers to create valid certificates with different fingerprints, allowing them to impersonate trusted entities.
There is no reliable workaround for CVE-2014-8275 other than upgrading to a secure version of OpenSSL.