The MD5 “SLOTH” vulnerability on TLS 1.2 affects Rational Performance Tester.
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.
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/S:U/C:H/I:L/A:N)
Rational Performance Tester version 8.2., 8.3., 8.5., 8.6. and 8.7.*.
It is strongly recommened to upgrade to version 9.0 which contains the fix for Bouncy Castle.
Customers affected by Java should continue to use the mitigating steps below until a fix is delivered for Java in version 9.0.0.1.
Mitigating steps for Bouncy Castle:
For Java disable support for MD5 and MD5with RSA. Mitigating steps involve editing the java.security file under the RPT product installation folder:
Update java.security file:
You should verify applying this configuration change does not cause any compatibility issues. Not disabling the MD5 signature hash 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 MD5 signature hash and take appropriate mitigation and remediation actions.