CVE-2014-0224: Weak Encryption
It was found that OpenSSL was vulnerable to a SSL/TLS MITM vulnerability. An attacker using a carefully crafted handshake can force the use of weak keying material in OpenSSL SSL/TLS clients and servers. This can be exploited by a Man-in-the-middle (MITM) attack where the attacker can decrypt and modify traffic from the attacked client and server. As per the upstream advisory: The attack can only be performed between a vulnerable client *and* server. OpenSSL clients are vulnerable in all versions of OpenSSL. Servers are only known to be vulnerable in OpenSSL 1.0.1 and 1.0.2-beta1. Users of OpenSSL servers earlier than 1.0.1 are advised to upgrade as a precaution. OpenSSL 0.9.8 SSL/TLS users (client and/or server) should upgrade to 0.9.8za. OpenSSL 1.0.0 SSL/TLS users (client and/or server) should upgrade to 1.0.0m. OpenSSL 1.0.1 SSL/TLS users (client and/or server) should upgrade to 1.0.1h. Acknowledgements: Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges KIKUCHI Masashi of Lepidum as the original reporter of this issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2014-0224?
CVE-2014-0224 is classified as a high severity vulnerability due to its potential to allow Man-in-the-Middle attacks and decrypt sensitive information.
How do I fix CVE-2014-0224?
To mitigate CVE-2014-0224, upgrade OpenSSL to version 1.0.1h or later, or 0.9.8za or later if using that version.
What systems are affected by CVE-2014-0224?
CVE-2014-0224 affects various OpenSSL versions, including 0.9.8 and 1.0.1, as well as dependent applications like Red Hat's JBoss platforms.
What type of attack does CVE-2014-0224 facilitate?
CVE-2014-0224 allows attackers to perform Man-in-the-Middle (MITM) attacks by exploiting weak keying materials negotiated during SSL/TLS handshakes.
Is it safe to use OpenSSL versions prior to 1.0.1h after CVE-2014-0224?
No, using OpenSSL versions prior to 1.0.1h poses significant security risks due to the vulnerabilities highlighted in CVE-2014-0224.