Security Bulletin
Summary
The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects Rational Synergy
Vulnerability Details
CVEID: CVE-2015-4000
DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as "Logjam".
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 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
· Rational Synergy release 7.2.1.3 ifix02 or earlier.
· Rational Synergy release 7.2.0.7 ifix01 or earlier.
Remediation/Fixes
|
Product | VRMF | APAR | Remediation/First Fix |
Rational Synergy | 7.2.0.x and 7.2.1.x | N/A | Replace the JRE used in Rational Synergy. Steps to download and replace JRE in Rational Synergy: 1. Open the list of Synergy downloads on Fix Central 2. Select the SDK and Readme for Rational Synergy which applied to your release as follows: Note: The fix will use the following naming convention: <V.R.M.F> -Rational-RATISYNE-JavaSE-SDK-6.0.16.5- <platform> Where <V.R.M.F> = release & <platform> = operating system o Rational Synergy 7.2.1 (uses 7.2.1.3 release designation) Example: 7.2.1.3-Rational-RATISYNE-JavaSE-SDK-6.0.16.5-Linux o Rational Synergy 7.2.0 (uses 7.2.0.7 release designation) Example: 7.2.0.7-Rational-RATISYNE-JavaSE-SDK-6.0.16.5-Windows Follow the steps in the HPUX_Install Instructions to replace the JRE if your Synergy Platform is on HPUX |
For Rational Synergy 7.1.0.x IBM recommends upgrading to a fixed, supported version/release/platform of the product.
You should verify applying this configuration change does not cause any compatibility issues. If you change the default setting after applying the fix, you 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 Diffie-Hellman key-exchange protocol used in TLS and take appropriate mitigation and remediation actions.
To verify if Synergy has JRE version to address this security vulnerability:-
Open a command prompt
Unix:-
Go to $CCM_HOME/jre/bin folder
Execute ./java -version
Windows:-
Go to %CCM_HOME%\jre\bin folder
Execute java -version
If in the output version is greater than SR16 FP5 or if it is SR16 FP5, It implies the run area has jre version that addressed this security vulnerability.
Example:-
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr16fp5-20150602_01(SR16 FP5))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr16fp4-201
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
Reported to IBM by The WeakDH team at https://weakdh.org
Change History
26th June 2015: 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:
22 December 2020
UID
swg21959743