Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect InfoSphere Streams (CVE-2014-6457, CVE-2014-3566, CVE-2014-3065)

Summary

There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 6 Service Refresh 16 Fix Pack 1 and Version 7R1 Service Refresh 1 Fix Pack 1 that is used by InfoSphere Streams. This also includes a fix for the Padding Oracle On Downgraded Legacy Encryption (POODLE) SSLv3 vulnerability (CVE-2014-3566). These were disclosed as part of the IBM Java SDK updates in October 2014.

Vulnerability Details

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)

CVE-ID: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.

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)

CVE-ID:CVE-2014-3065

**DESCRIPTION:**IBM Java SDK contains a vulnerability in which the default configuration for the shared classes feature potentially allows arbitrary code to be injected into the shared classes cache, which may subsequently be executed by other local users.

CVSS Base Score: 6
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/93629 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:H/Au:S/C:C/I:C/A:C)

Affected Products and Versions

• • 1.2.1.0
• 2.0.0.4 and earlier
• 3.0.0.4 and earlier
• 3.1.0.4 and earlier
• 3.2.1.2 and earlier

Remediation/Fixes

Apply the appropriate upgrade for InfoSphere Streams as indicated below. Fix packs are available on IBM Fix Central.

• Version 3.2.1: Apply 3.2.1 fix pack 3 (3.2.1.3) or higher. If JAVA_HOME is defined see the note at the end of this section.
• Version 3.1: Apply 3.1 fix pack 5 (3.1.0.5) or higher. If JAVA_HOME is defined see the note at the end of this section.
• Version 3.0: Apply 3.0 fix pack 5 (3.0.0.5) or higher. If JAVA_HOME is defined see the note at the end of this section.
• Versions 1.0 and 2.0: Upgrade to the latest version of InfoSphere Streams for which these fixes have been released.
• For assistance performing an upgrade contact IBM Technical Support.
• Customers who cannot upgrade and need to secure their installation should open a PMR with IBM Technical Support and request assistance securing their InfoSphere Streams system against the vulnerabilities identified in this Security Bulletin.

IMPORTANT NOTE: If JAVA_HOME is set ensure it points to the install location of the upgraded IBM Developer Kit, Java. Applications compiled with JAVA_HOME set to a different location will need to be recompiled after JAVA_HOME has been changed. For more information on compiling with JAVA_HOME set see the Notes section on the page at this URL: http://www-01.ibm.com/support/knowledgecenter/SSCRJU_3.2.1/com.ibm.swg.im.infosphere.streams.install-admin.doc/doc/ibminfospherestreams-install-prerequisites-java-supported-sdks.html?lang=en

For version 1.x and 2.x IBM recommends upgrading to a fixed, supported version/release/platform of the product.

Workarounds and Mitigations

For customers not applying the fixpacks above, mitigation for the following vulnerabilities on the listed versions can be obtained by following the instructions below:

• **CVE-2014-3566: SSL v3 POODLE attack (Streams 3.2.1.x): **Mitigation for this vulnerability in the SWS server for Streams version 3.2.1 can be obtained by enabling the exclusive use of TLS1.2 and above by setting SWS.sslProtocol=TLSv1.2 as described in the documentation here:
  <http://www-01.ibm.com/support/knowledgecenter/SSCRJU_3.2.1/com.ibm.swg.im.infosphere.streams.admin.doc/doc/ibminfospherestreams-sws-protocol.html&gt;
  • • **CVE-2014-3065: Java shared cl****asses (Streams v 2.0.x and above) **Mitigation for this vulnerability in Streamtool for Streams version 2.0 and above can be obtained by creating a secured directory and specifying it as the Java cache location in the streamtool.java.properties file. Refer to the documentation found at: <http://www-01.ibm.com/support/knowledgecenter/SSCRJU_3.2.1/com.ibm.swg.im.infosphere.streams.install-admin.doc/doc/ibminfospherestreams-planning-performance-java-cache-commands.html?lang=en&gt;

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.