Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server January 2016 CPU (CVE-2016-0475, CVE-2016-0466, CVE-2015-7575, CVE-2016-0448)

Summary

There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server. These issues were disclosed as part of the IBM Java SDK updates in January 2016 and includes the vulnerability commonly referred to as “SLOTH”. These may affect some configurations of IBM WebSphere Application Server Full Profile, IBM WebSphere Application Server Liberty Profile, and IBM WebSphere Application Server Hypervisor Edition.

Vulnerability Details

This bulletin covers all applicable Java SE CVE’s published by Oracle as part of their January 2016 Critical Patch Update which affects IBM SDK, Java Technology Edition. There are other advisories included in the IBM Java SDK but WebSphere Application Server is not vulnerable to them. You will need to evaluate your own code to determine if you are vulnerable. Please refer to the Reference section for more information on the advisories not applicable to WebSphere Application Server.

CVEID: CVE-2016-0475**
DESCRIPTION:** An unspecified vulnerability related to the Libraries component has partial confidentiality impact, partial integrity impact, and no availability impact.
CVSS Base Score: 5.8
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109946 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:N)

CVEID: CVE-2016-0466**
DESCRIPTION:** An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109948 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)

CVEID: CVE-2015-7575**
DESCRIPTION:** The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials. This vulnerability is commonly known as “SLOTH”.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/UI:U/C:H/I:L/A:N)

CVEID: CVE-2016-0448**
DESCRIPTION:** An unspecified vulnerability related to the JMX component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109949 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N)

Affected Products and Versions

IBM Java SDK shipped with IBM WebSphere Application Server Version 8.5.0.0 through 8.5.5.8, Version 8.0.0.0 through 8.0.0.12, Version 7.0.0.0 through 7.0.0.39.

• This does not occur on IBM Java SDK shipped with WebSphere Application Servers Fix Packs 8.5.5.9, 8.0.0.13 and 7.0.0.41 or later.

• Remediation/Fixes

PLEASE NOTE:

After you have applied the correct Interim Fix as noted below for your version of the IBM SDK Java Technology Edition. You will also need to manually update your WASHOME/java/jre/lib/security/java.security file (unless you are using WebSphere Application Server Liberty) to add MD5 and MD5withRSA as noted below:

   jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, **MD5withRSA**





   jdk.certpath.disabledAlgorithms=MD2, RSA keySize <1024, **MD5**

--OR–

** **You can choose to apply Interim Fix PI54960 to the WebSphere Application Server Full Profile. This interim fix will programatically update those values for you during the SSL initialization. Link to Interim Fix PI54960

The java.security file updates are not needed for WebSphere Application Server Liberty.

Download and apply the interim fix APARs below, for your appropriate release

For the IBM Java SDK updates:
For V8.5.0.0 through 8.5.5.8 WebSphere Application Server Liberty:
Upgrade to WebSphere Application Server Liberty Profile Fix Packs as noted below or later fix pack level and apply one of the interim fixes below:

• Upgrade to WebSphere Application Server Liberty Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55779: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 20 (optional)

• Upgrade to WebSphere Application Server Liberty Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55776: Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 9 Fix Pack 30 (optional)

• Upgrade to WebSphere Application Server Liberty Profile Fix Pack 8.5.5.2 or later then apply Interim Fix PI55775: Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 3 Fix Pack 30 (optional)

• Upgrade to WebSphere Application Server Liberty Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55773: Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 2 Fix Pack 10 (optional)

• For a Liberty Archive Fix - Upgrade to WebSphere Application Server Liberty Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55774: Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 2 Fix Pack 10 (optional)
  --OR–

• Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 9 (8.5.5.9) or later.

For V8.5.0.0 through 8.5.5.8 WebSphere Application Server Full Profile and WebSphere Application Server Hypervisor Edition**:**

Upgrade to WebSphere Application Server Full Profile Fix Packs as noted below or later fix pack level and then apply one of the interim fixes below:

• Upgrade to WebSphere Application Server Full Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55778: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 20 (required)

• Upgrade to WebSphere Application Server Full Profile Fix Pack 8.5.5.1 or later then apply Interim Fix PI55776: Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 9 Fix Pack 30 (optional)

• Upgrade to WebSphere Application Server Full Profile Fix Pack 8.5.5.2 or later then apply Interim Fix PI55775: Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 3 Fix Pack 30 (optional)
  --OR–

• Apply IBM Java SDK shipped with the WebSphere Application Server Fix pack 9 (8.5.5.9) or later.
  **

For V8.0.0.0 through 8.0.0.12 WebSphere Application Server and WebSphere Application Server Hypervisor Edition:**

Upgrade to WebSphere Application Server Fix Pack 8.0.0.7 or later then apply the interim fix below:

• Apply Interim Fix PI55780: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 20
  --OR–

• Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 13 (8.0.0.13) or later.
  **
  For V7.0.0.0 through 7.0.0.39 WebSphere Application Server and WebSphere Application Server Hypervisor Edition:**

Upgrade to WebSphere Application Server Fix Pack 7.0.0.31 or later then apply the interim fix below:

• Apply Interim Fix PI55781: Will upgrade you to IBM SDK, Java Technology Edition, Version 6 Service Refresh 16 Fix Pack 20
  --OR–

• Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 41 (7.0.0.41) or later.

If you are using the Daemon address space, please logon to the security portal to get further instructions.

For unsupported versions of the above products, IBM recommends upgrading to a fixed, supported version of the product.

Workarounds and Mitigations

For CVE-2015-7575:

Users of Java 7 and later can address the issue by updating the WASHOME/java/jre/lib/security/java.security file as follows (both steps are required):

· Add MD5 to the jdk.certpath.disabledAlgorithms property - e.g. jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024, MD5

· Add MD5withRSA to the jdk.tls.disabledAlgorithms property - e.g. jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768, MD5withRSA

Java 6 requires code changes in the JSSE component in addition to the java.security file modifications, so upgrading the SDK is the only solution.