high
7.4
CWE
326
Advisory Published
CVE Published
Updated

CVE-2014-0224: Weak Encryption

First published: Mon Jun 02 2014(Updated: )

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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/openssl<1.0.1
1.0.1
redhat/openssl<0.9.8
0.9.8
OpenSSL<0.9.8za
OpenSSL>=1.0.0<1.0.0m
OpenSSL>=1.0.1<1.0.1h
JBoss Enterprise Application Platform=5.2.0
JBoss Enterprise Application Platform=6.2.3
Red Hat JBoss Enterprise Web Platform=5.2.0
Red Hat JBoss Enterprise Web Server=2.0.1
Red Hat Storage=2.1
Red Hat Fedora=19
Red Hat Fedora=20
openSUSE=13.1
openSUSE=13.2
Red Hat Enterprise Linux=4
Red Hat Enterprise Linux=5
Red Hat Enterprise Linux=6.0
FileZilla Server<0.9.45
Siemens Application Processing Engine<2.0.2
Siemens Application Processing Engine
Siemens CP 1543-1<1.1.25
Siemens CP 1543-1
Siemens S7-1500 Modular Controllers<1.6
Siemens Simatic S7-1500 ET 200pro
Siemens ROX<1.16.1
Siemens Ruggedcom ROX
MariaDB>=10.0.0<10.0.13
Python 2.7>=2.7.0<2.7.8
Python 2.7>=3.4.0<3.4.2
Node.js<0.10.29

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html

Remedy

https://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=bc8923b1ec9c467755cd86f7848c50ee8812e441

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203