The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM Rational ClearQuest.
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
IBM Rational ClearQuest, versions 7.1.0.x, 7.1.1.x, 7.1.2.x, 8.0.0.x, 8.0.1.x, in the following components:
- ClearQuest Web Server
- ClearQuest Report Server
- ClearQuest Full Text Search Server
- Customer defined uses of SSL from cqperl scripts
- ClearQuest DataDirect when SSL is enabled for Oracle connections
Applying the fix
8.0.1 through 220.127.116.11
|Install Rational ClearQuest Fix Pack 10 (18.104.22.168) for 8.0.1.|
8.0 through 22.214.171.124
|Install Rational ClearQuest Fix Pack 17 (126.96.36.199) for 8.0.|
7.1.2 through 188.8.131.52
|Customers on extended support contracts should install Rational ClearQuest Fix Pack 19 (184.108.40.206) for 7.1.2. If you enable SSL for your Oracle database, see the "Workarounds and Mitigations" section below.|
7.1.1.x (all fix packs)
7.1.0.x (all fix packs)
|Customers on extended support contracts should contact Rational Customer Support|
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.
For unsupported versions, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
Workarounds and Mitigations
If you are not upgrading to ClearQuest Fix Pack 17 for 8.0 or ClearQuest Fix Pack 10 for 8.0.1, and you enable SSL for your Oracle database, then you will need to take further steps to mitigate the issue.
1. Please refer the following link to specify "SSL_RSA_WITH_3DES_EDE_CBC_SHA" as the only Cipher Suite supported on the database server
Get Notified about Future Security Bulletins
Reported to IBM by The WeakDH team at https://weakdh.org
*31 Jul 2015: Original copy published
*16 Sep 2015: Add the DataDirect component and the workaround to avoid this vulnerability, and refer to newly published fix pack for the other component fixes
*9 Dec 2015: Upgrade to latest fixpacks to secure Oracle SSL connections.
*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.
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
Internal Use Only
For 7.1.0.x and 7.1.1.x customers that have support extensions with security included: the security fixes are not available on 7.1.1.x, the solution is to upgrade to 7.1.2.x. All security-supported 7.1.x customers are OK with this except Lloyds, who have not answered our repeated questions trying to get them to either agree or disagree with no security fixes on 7.1.1.x.
DataDirect fix was included in 220.127.116.11 and 18.104.22.168
17 June 2018