Security Bulletin: Vulnerability in SSLv3 affects Rational Change (CVE-2014-3566)

Summary

SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled in Rational Change.

Vulnerability Details

| Subscribe to My Notifications to be notified of important product support alerts like this.

• Follow this link for more information (requires login with your IBM ID)
  —|—

CVE-ID: CVE-2014-3566

Description: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.

CVSS Base Score: 4.3 **CVSS Temporal Score: **See <https://exchange.xforce.ibmcloud.com/vulnerabilities/97013&gt;_ _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 Change: 5.2, 5.3, 5.3.1

Remediation/Fixes

Product

| VRMF|APAR|Remediation/First Fix
—|—|—|—
Rational Change| 5.2| None| Upgrade to Rational Change Interim Fix 6 for 5.2.0.8 and see workaround for mitigation steps.
Rational Change| 5.3| None| See workaround
Rational Change| 5.3.1| None| See workaround

Workarounds and Mitigations

Mitigation is to disable SSLv3 protocol following steps below.

Change 5.2:
Once https is configured, add additional argument <Set name="SSLProtocol">TLS</Set> just after the line <Set name="KeyPassword"></Set> in jetty\etc\change.xml file.

Change 5.3:
Once https is configured, add additional argument <Set name="SSLProtocol">TLS</Set> just after the line <Set name="KeyPassword"></Set> in jetty\etc\jetty.xml file.

Change 5.3.1:
Once https is configured, add additional argument <Set name="protocol">TLS</Set> just after the line <Set name="TrustStorePassword"></Set> in jetty\etc\jetty.xml file.

IBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3.