Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server October 2014 CPU

Summary

There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server. This also includes a fix for the Padding Oracle On Downgraded Legacy Encryption (POODLE) SSLv3 vulnerability (CVE-2014-3566). These issues were disclosed as part of the IBM Java SDK updates in October 2014.

Vulnerability Details

The following advisories are included in the IBM® SDK Java™ Technology Edition and WebSphere Application Server may be vulnerable to them. Interim fixes for HP Platforms are now available.

CVEID: CVE-2014-6512

DESCRIPTION: An unspecified vulnerability related to the Libraries component has no confidentiality impact, partial integrity impact, and no availability impact.

CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97147 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)

CVEID: CVE-2014-6457

DESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.

CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97148 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)

CVEID: CVE-2014-6558

DESCRIPTION: An unspecified vulnerability related to the Security component has no confidentiality impact, partial integrity impact, and no availability impact.

CVSS Base Score: 2.6
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97151 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:N/I:P/A:N)

CVEID:CVE-2014-3566

**DESCRIPTION:**Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections. The IBM SDK for Java has changed the default to eliminate the POODLE vulnerability. There is a new system property com.ibm.jsse2.disableSSLv3 It is defaulted to true so that it will not use SSLv3. If you want to take the risk you may turn SSLv3 back on with the system property: com.ibm.jsse2.disableSSLv3=false

CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)

For more information on CVE-2014-3566, please refer to the links in the reference section.

The following advisories are included in the IBM SDK for Java 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: ** **
CVE IDs: **CVEID: **CVE-2014-3065 CVEID:CVE-2014-4288 CVEID:CVE-2014-6456 CVEID:CVE-2014-6458 CVEID:CVE-2014-6466 **CVEID: **CVE-2014-6468 CVEID:CVE-2014-6476 CVEID:CVE-2014-6492 CVEID:CVE-2014-6493 CVEID:CVE-2014-6502 CVEID:CVE-2014-6503 CVEID: CVE-2014-6504 CVEID:CVE-2014-6506 CVEID:CVE-2014-6511 CVEID: CVE-2014-6513
CVEID:CVE-2014-6515 **CVEID: **CVE-2014-6519 CVEID:CVE-2014-6527 CVEID:CVE-2014-6531 CVEID: CVE-2014-6532

Affected Products and Versions

IBM Java SDK shipped with IBM WebSphere Application Server Version 8.5.0.0 through 8.5.5.3, Version 8.0.0.0 through 8.0.0.9, Version 7.0.0.0 through 7.0.0.35, Version 6.1.0.0 through 6.1.0.47. This does not occur on IBM Java SDK shipped with WebSphere Application Servers Fix Packs 8.5.5.4, 8.0.0.10 and 7.0.0.37 or later.

Warning:
For mixed cells that contain WebSphere Application Server version 6.0.2 nodes where Java 2 security is enabled, ensure APAR PM92206 or its circumvention is applied to the Deployment Manager to prevent sync operation failure. PM92206 has been delivered with an Interim Fix or with WebSphere Application Server Fix Packs 8.5.5.1 and 8.0.0.7 and 7.0.0.31 or later.

Remediation/Fixes

For IBM WebSphere Application Server and IBM WebSphere Application Server Hypervisor Edition****:

Download and apply the interim fix APARs below, for your appropriate release:
**
For V8.5.0.0 through 8.5.5.3 Full Profile:**

• Apply Interim Fix PI27099: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 2 (required)

• Apply Interim Fix PI27097: Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 2 (optional)

• Apply Interim Fix PI27098: Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 8 (optional)

• --OR–

• Apply IBM Java SDK shipped with the WebSphere Application Server Fix pack 4 (8.5.5.4) or later.
  **
  For 8.0.0.0 through 8.0.0.9:**

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

• Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 10 (8.0.0.10) or later.
  **
  For V7.0.0.0 through 7.0.0.35:**

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

• Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 37 (7.0.0.37) or later.
  **
  For V6.1.0.0 through 6.1.0.47:**

• Contact IBM Support and apply Interim Fix PI27103: Will upgrade you to IBM SDK, Java 2 Technology Edition, Version 5.0 Service Refresh 16 Fix Pack 8
  _
  For IBM WebSphere Application Server for i5/OS operating systems:_

The IBM Developer Kit for Java is prerequisite software for WebSphere Application Server for IBM i. Please refer to Java on IBM i for updates on when these fixes will be available.

Workarounds and Mitigations

IBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues.

**

**