CVE-2016-2183: openssl 1.0.2h vulnerabilities

Published Aug 23, 2016
·
Updated

A flaw was found in the way the DES/3DES cipher was used as part of the TLS/SSL protocol. A man-in-the-middle attacker could use this flaw to recover some plaintext data by capturing large amounts of encrypted traffic between TLS/SSL server and client if the communication used a DES/3DES based ciphersuite.

Other sources

Ciphers with 64-bit block sizes used in CBC mode were found to be vulnerable to birthday attack when key renegotiation doesn't happen frequently or at all in long running connections. 3DES cipher as used in TLS protocol is vulnerable to this attack, that allows remote attacker to recover partial plaintext information (XOR of two plaintext blocks).

— Red Hat

SWEET32 is a new attack on older block cipher algorithms that use a block size of 64 bits.

As mitigation, OpenSSL has moved DES-based ciphers from the HIGH to MEDIUM group. As Node.js includes HIGH, but not MEDIUM, in its default suite, affected ciphers are no longer included unless the default suite is not used. Node's default TLS cipher suite can be found in the API documentation.

— Node.Js

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec pro ...

— Debian

Affected Software

72 affected componentsFixes available
redhat/jbcs-httpd24-httpd<0:2.4.23-122.jbcs.el6
0:2.4.23-122.jbcs.el6
redhat/jbcs-httpd24-openssl<1:1.0.2h-14.jbcs.el6
1:1.0.2h-14.jbcs.el6
redhat/jbcs-httpd24-httpd<0:2.4.23-122.jbcs.el7
0:2.4.23-122.jbcs.el7
redhat/jbcs-httpd24-openssl<1:1.0.2h-14.jbcs.el7
1:1.0.2h-14.jbcs.el7
redhat/java<1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
redhat/java<1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
redhat/java<1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
redhat/java<1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
redhat/java<1.8.0-ibm-1:1.8.0.4.1-1jpp.1.el6_8
1.8.0-ibm-1:1.8.0.4.1-1jpp.1.el6_8
redhat/python<0:2.7.5-69.el7_5
0:2.7.5-69.el7_5
redhat/java<1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
redhat/java<1.8.0-ibm-1:1.8.0.4.1-1jpp.2.el7
1.8.0-ibm-1:1.8.0.4.1-1jpp.2.el7
redhat/httpd<0:2.2.26-57.ep6.el6
0:2.2.26-57.ep6.el6
redhat/httpd22<0:2.2.26-58.ep6.el7
0:2.2.26-58.ep6.el7
redhat/tomcat6<0:6.0.41-19_patch_04.ep6.el6
0:6.0.41-19_patch_04.ep6.el6
redhat/tomcat7<0:7.0.54-28_patch_05.ep6.el6
0:7.0.54-28_patch_05.ep6.el6
redhat/tomcat6<0:6.0.41-19_patch_04.ep6.el7
0:6.0.41-19_patch_04.ep6.el7
redhat/tomcat7<0:7.0.54-28_patch_05.ep6.el7
0:7.0.54-28_patch_05.ep6.el7
GE Vulnerabilities related to SSH Support: firmware versions 7.4x to 8.0x (CyberSentry option)
GE Web server vulnerabilities: all firmware versions prior to version 8.1x
GE Protection from unintended firmware upload: all firmware versions prior to 8.1x with basic security option
GE Provisions to disable Factory Mode: all firmware versions prior to 8.1x with basic security option
GE Access to “Last-key pressed” register: all firmware versions prior to 8.1x with basic security option
GE Weakness in UR bootloader binary: all bootloader versions prior to 7.03/7.04
redhat JBoss Enterprise Application Platform=6.0.0
redhat Jboss Enterprise Web Server=1.0.0
redhat Jboss Enterprise Web Server=2.0.0
redhat Jboss Web Server=3.0
redhat Enterprise Linux=5.0
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
Python Python>=2.7.0<2.7.13
Python Python>=3.4.0<3.4.7
Python Python>=3.5.0<3.5.3
Cisco Content Security Management Appliance=9.6.6-068
Cisco Content Security Management Appliance=9.7.0-006
OpenSSL OpenSSL=1.0.1a
OpenSSL OpenSSL=1.0.1b
OpenSSL OpenSSL=1.0.1c
OpenSSL OpenSSL=1.0.1d
OpenSSL OpenSSL=1.0.1e
OpenSSL OpenSSL=1.0.1f
OpenSSL OpenSSL=1.0.1g
OpenSSL OpenSSL=1.0.1h
OpenSSL OpenSSL=1.0.1i
OpenSSL OpenSSL=1.0.1j
OpenSSL OpenSSL=1.0.1k
OpenSSL OpenSSL=1.0.1l
OpenSSL OpenSSL=1.0.1m
OpenSSL OpenSSL=1.0.1n
OpenSSL OpenSSL=1.0.1o
OpenSSL OpenSSL=1.0.1p
OpenSSL OpenSSL=1.0.1q
OpenSSL OpenSSL=1.0.1r
OpenSSL OpenSSL=1.0.1t
OpenSSL OpenSSL=1.0.2a
OpenSSL OpenSSL=1.0.2b
OpenSSL OpenSSL=1.0.2c
OpenSSL OpenSSL=1.0.2d
OpenSSL OpenSSL=1.0.2e
OpenSSL OpenSSL=1.0.2f
OpenSSL OpenSSL=1.0.2h
Oracle Database=11.2.0.4
Oracle Database=12.1.0.2
Nodejs Node.js>=0.10.0<0.10.47
Nodejs Node.js>=0.12.0<0.12.16
Nodejs Node.js>=4.0.0<4.1.2
Nodejs Node.js>=4.2.0<4.6.0
Nodejs Node.js>=6.0.0<6.7.0
Node.js Node.js>=4.0.0<4.6.0, >=5.0.0<6.0.0, >=6.0.0<6.7.0
4.6.06.7.0
Node.js Node.js>=4.0.0<4.6.0
4.6.0
Node.js Node.js>=6.0.0<6.7.0
6.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.23-122.jbcs.el6
  2. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2h-14.jbcs.el6
  3. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.23-122.jbcs.el7
  4. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2h-14.jbcs.el7
  5. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
  6. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
  7. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
  8. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
  9. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-ibm-1:1.8.0.4.1-1jpp.1.el6_8
  10. Upgrade

    Upgrade redhat/python to a version that resolves this vulnerability.

    Fixed in 0:2.7.5-69.el7_5
  11. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
  12. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-ibm-1:1.8.0.4.1-1jpp.2.el7
  13. Upgrade

    Upgrade redhat/httpd to a version that resolves this vulnerability.

    Fixed in 0:2.2.26-57.ep6.el6
  14. Upgrade

    Upgrade redhat/httpd22 to a version that resolves this vulnerability.

    Fixed in 0:2.2.26-58.ep6.el7
  15. Upgrade

    Upgrade redhat/tomcat6 to a version that resolves this vulnerability.

    Fixed in 0:6.0.41-19_patch_04.ep6.el6
  16. Upgrade

    Upgrade redhat/tomcat7 to a version that resolves this vulnerability.

    Fixed in 0:7.0.54-28_patch_05.ep6.el6
  17. Upgrade

    Upgrade redhat/tomcat6 to a version that resolves this vulnerability.

    Fixed in 0:6.0.41-19_patch_04.ep6.el7
  18. Upgrade

    Upgrade redhat/tomcat7 to a version that resolves this vulnerability.

    Fixed in 0:7.0.54-28_patch_05.ep6.el7
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.0Fixed in 6.7.0
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.0
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.7.0
  22. Configuration

    Disable vulnerable DES and 3DES cipher suites, including 3DES-CBC, in the applicable TLS component and prefer AES-based cipher suites; do not disable AES-128 or AES-256 cipher suites.

    TLS/SSL configuration DES/3DES cipher suites = disabled

Event History

Aug 23, 2016
Data Sourced
via Red Hat·09:15 AM
DescriptionSeverityAffected Software
Aug 24, 2016
CVE Published
12:00 AM
Sep 1, 2016
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·12:59 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·12:59 AM
DescriptionSeverity
Sep 28, 2016
Data Sourced
via Node.js·12:43 AM
Severity
Data Sourced
via Node.js·12:47 AM
Affected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2016-2183?

CVE-2016-2183 is considered a medium severity vulnerability due to its potential impact on encrypted data.

2

How do I fix CVE-2016-2183?

To fix CVE-2016-2183, upgrade to the recommended versions specified by your affected packages, including jbcs-httpd24-httpd and jbcs-httpd24-openssl.

3

What systems are affected by CVE-2016-2183?

CVE-2016-2183 affects systems using DES/3DES ciphers as part of the TLS/SSL protocol, particularly those under Red Hat's supported packages.

4

What are the risks associated with CVE-2016-2183?

The primary risk of CVE-2016-2183 is that an attacker could conduct a man-in-the-middle attack to recover plaintext data from TLS/SSL communications.

5

Is there a workaround for CVE-2016-2183?

While upgrading is the most effective solution, temporarily disabling DES/3DES cipher suites can serve as a workaround until systems are updated.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203