Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect WebSphere DataPower XC10 Appliance (CVE-2016-3427, CVE-2016-3426)

Summary

There are multiple vulnerabilities in IBM® Runtime Environment Java™ Technology Edition, Versions 6 and 7 that are used by WebSphere DataPower XC10 Appliance. These issues were disclosed as part of the IBM Java SDK updates in April 2016.

Vulnerability Details

CVEID: CVE-2016-3427**
DESCRIPTION:** An unspecified vulnerability related to the JMX component has complete confidentiality impact, complete integrity impact, and complete availability impact.
CVSS Base Score: 10
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112459 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)

CVEID: CVE-2016-3426**
DESCRIPTION:** An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information resulting in a partial confidentiality impact using unknown attack vectors.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112457 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)

Affected Products and Versions

WebSphere DataPower XC10 Appliance Version 2.1
WebSphere DataPower XC10 Appliance Version 2.5

Remediation/Fixes

Apply an interim fix, according to the table below.** **Interim fixes are associated with the original APAR that is documented in the table. Because these APAR references might be updated to more recent APARs, see the links in the table for the most recent interim fix information.

This interim fix contains a new default SSL certificate, as the previous default SSL certificate, which was never intended for production use, has an MD5 signature and is no longer compatible with Java. For deployments that have not installed XC10 interim fixes since February 26, 2016, the following applies: installing this interim fix will make it incompatible with any WebSphere Datapower XC10 appliances that are running with an MD5 certificate, including the default SSL certificate that was shipped prior to this interim fix. If the appliance is configured with a custom keystore and certificate with an MD5 signature, it must be replaced prior to upgrading to this interim fix or the ‘clear-tls-config’ command must be run on the appliance before or after performing the upgrade. Failing to do so will result in the appliance failing to start. Note that changing the active certificate for an appliance collective does require that the cache be reloaded and client truststores must be configured to trust the new certificate.

Workarounds and Mitigations

There is no workaround. The interim fix must be applied to correct the problem.