Security Bulletin
Summary
There are multiple vulnerabilities in IBM® Runtime Environment Java™ Technology Edition, Version 6 that is used by IBM Cognos Command Center. These issues were disclosed as part of the IBM Java SDK updates in January 2016 and includes the vulnerability commonly referred to as “SLOTH”.
Vulnerability Details
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 referred to 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)
Affected Products and Versions
IBM Cognos Command Center 10.1 All Editions
IBM Cognos Command Center 10.2 All Editions
IBM Cognos Command Center 10.2.1 All Editions
IBM Cognos Command Center 10.2.2 All Editions
IBM Cognos Command Center 10.2.3 All Editions
Remediation/Fixes
The recommended solution is to apply the IBM JRE 6.0 SR16FP20 to the affected versions of
IBM Cognos Command Center.
The fix for all affected versions is found here: http://www.ibm.com/support/fixcentral/swg/quickorder?parent=Cognos&product=ibm/Information+Management/Cognos+Command+Center&release=10.2.3&platform=Windows+32-bit,+x86&function=fixId&fixids=10.2.3-BA-CCC-Win32-JRE-60SR16FP20
Installation instructions for applying this fix.
For Microsoft Windows servers where the Agent or the Server component is installed please follow this procedure:
Step 1:
Download the 32 bit IBM Java JRE (file name: ibm-java-jre-60-win-i386.zip, Size: 80.6 MB, Build: pwi3260sr16fp20-20160111_01(SR16 FP20)).
Step 2:
Stop the CccServer, CccQueue and CccAgent Microsoft Windows services.
Step 3:
For IBM Cognos Command Center 10.1 and 10.2: Rename the <INSTALLDIR>\Common\java directory to <INSTALLDIR>\Common\java.orig
For IBM Cognos Command Center 10.2.1:Rename the <INSTALLDIR>\Common\java.6.0.16.0 directory to <INSTALLDIR>\Common\java.6.0.16.0.orig
For IBM Cognos Command Center 10.2.2 and 10.2.3: Rename the <INSTALLDIR>\Common\java.6.0.16 directory to <INSTALLDIR>\Common\java.6.0.16.orig
Step 4:
For IBM Cognos Command Center 10.1 and 10.2: Unpack the content of the ibm-java-jre-60-win-i386.zip file to <INSTALLDIR>\Common\java
For IBM Cognos Command Center 10.2.1: Unpack the content of the ibm-java-jre-60-win-i386.zip file to <INSTALLDIR>\Common\java.6.0.16.0
For IBM Cognos Command Center 10.2.2 and 10.2.3: Unpack the content of the ibm-java-jre-60-win-i386.zip file to <INSTALLDIR>\Common\java.6.0.16.
Step 5:
Start the CccAgent, CccQueue and CccServer Microsoft Windows services.
Step 6:
Validate the installation by testing the connectivity to the agent using the CCC Client.
Upgrade instructions after applying this fix.
For all IBM Cognos Command Center installations with the above fix applied:
Before upgrading your installation to a newer version please revert to the original \java\ directory by following this procedure.
Please note, the directory called \java\ could also be \java.6.0.16.0\ or \java.6.0.16\ depending on your IBM Cognos Command Center version.
Step A:
Stop the CccServer, CccQueue and CccAgent Windows services.
Step B:
Rename the <INSTALLDIR>\Common\java directory to <INSTALLDIR>\Common\java.cve
Step c:
Rename the <INSTALLDIR>\Common\java.orig directory to <INSTALLDIR>\Common\java
Step D:
Proceed to upgrade your Cognos Command Center installation to a newer version.
Step E:
After the upgrade to the newer version is done, please reapply this fix starting from Step 1.
You should verify applying this fix does not cause any compatibility issues.
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
CVE-2015-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France
Change History
9 February 2016 Original Version Published.
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21975832