Security Bulletin: Vulnerability in RC4 stream cipher affects IMS™ Enterprise Suite: Connect API for Java, SOAP Gateway, and Explorer for Development (CVE-2015-2808)

Summary

There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, IBM SDK, Java Technology Edition, Version 7 Service Refresh 8 that is used the following IMS™ Enterprise Suite components: Connect API for Java, SOAP Gateway, and Explorer for Development. This bulletin also addresses the The RC4 “Bar Mitzvah” Attack for SSL/TLS client and server vulnerability.

The Bar Mitzvah Attack exploits a previously known vulnerability in the RC4 component of the SSL/TLS communication protocols. This exploit allows the attacker to partially decrypt information sent between two computer systems across a network. This can be a serious security issue because RC4 reportedly protects as much as 30 percent of Internet SSL traffic and decrypted material may include passwords, credit card numbers, browser cookies, etc.

Vulnerability Details

CVEID: CVE-2015-2808 DESCRIPTION: The RC4 algorithm, as used in the TLS protocol and SSL protocol, could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability to remotely expose account credentials without requiring an active man-in-the-middle session. Successful exploitation could allow an attacker to retrieve credit card data or other sensitive information. This vulnerability is commonly referred to as “Bar Mitzvah Attack”.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/101851 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)

Affected Products and Versions

Explorer for Development of the IMS™ Enterprise Suite Versions 3.1 and earlier.

The SOAP Gateway component of the IMS™ Enterprise Suite Versions 3.1 and earlier.

Connect API for Java component of the IMS™ Enterprise Suite Versions 3.1 and earlier.

Workarounds and Mitigations

1. Disabling RC4. This can be achieved by adding RC4 to the list of disabled algorithms defined by the jdk.tls.disabledAlgorithms security property in java.security file

2. Not explicit enabling the RC4 cipher suite(s)

3. For HttpsURLConnection, set https.cipherSuites system property to not include RC4 cipher suites.

You should verify applying this configuration change does not cause any compatibility issues. Not disabling the RC4 stream cipher will expose yourself to the attack described above. IBM recommends that you review your entire environment to identify other areas where you have enabled the RC4 stream cipher and take appropriate mitigation and remediation actions.