high
7.5
CWE
327 200 326
Advisory Published
CVE Published
CVE Published
Updated

CVE-2016-2183: Infoleak

First published: Tue 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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
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 Web Server
GE Access
GE Access
GE Access
GE Access
GE UR bootloader binary
JBoss Enterprise Application Platform=6.0.0
Red Hat JBoss Enterprise Web Server=1.0.0
Red Hat JBoss Enterprise Web Server=2.0.0
Red Hat JBoss Web=3.0
Red Hat Enterprise Linux=5.0
Red Hat Enterprise Linux=6.0
Red Hat Enterprise Linux=7.0
Python 2.7>=2.7.0<2.7.13
Python 2.7>=3.4.0<3.4.7
Python 2.7>=3.5.0<3.5.3
Cisco Content Security Management=9.6.6-068
Cisco Content Security Management=9.7.0-006
OpenSSL=1.0.1a
OpenSSL=1.0.1b
OpenSSL=1.0.1c
OpenSSL=1.0.1d
OpenSSL=1.0.1e
OpenSSL=1.0.1f
OpenSSL=1.0.1g
OpenSSL=1.0.1h
OpenSSL=1.0.1i
OpenSSL=1.0.1j
OpenSSL=1.0.1k
OpenSSL=1.0.1l
OpenSSL=1.0.1m
OpenSSL=1.0.1n
OpenSSL=1.0.1o
OpenSSL=1.0.1p
OpenSSL=1.0.1q
OpenSSL=1.0.1r
OpenSSL=1.0.1t
OpenSSL=1.0.2a
OpenSSL=1.0.2b
OpenSSL=1.0.2c
OpenSSL=1.0.2d
OpenSSL=1.0.2e
OpenSSL=1.0.2f
OpenSSL=1.0.2h
Oracle Database=11.2.0.4
Oracle Database=12.1.0.2
Node.js>=0.10.0<0.10.47
Node.js>=0.12.0<0.12.16
Node.js>=4.0.0<4.1.2
Node.js>=4.2.0<4.6.0
Node.js>=6.0.0<6.7.0

Remedy

1.SSL/TLS configurations should prefer AES over DES. Versions of OpenSSL shipped with Red Hat Enterprise Linux 6 and 7 already do so. In the version of OpenSSL shipped with Red Hat Enterprise Linux 5, 3DES is listed below the AES-256 cipher and above the AES-128 cipher, therefore AES-256 based ciphersuite should not be disabled on the server. 2. Servers using OpenSSL, should not disable AES-128 and AES-256 ciphersuites. Versions of Apache shipped with Red Hat Enterprise Linux use the default cipher string, in which AES is preferred over DES/3DES based ciphersuites. For JBoss Middleware, and Java mitigations, please review this knowledge base article: https://access.redhat.com/articles/2598471 This can be mitigated on OpenShift Container Platform (OCP) by disabling the vulnerable TLS cipher suite in the applicable component. TLS configuration options for OCP are described here: https://access.redhat.com/articles/5348961

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.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://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html

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

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • 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.

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