Security Bulletin: Vulnerability in SSLv3 affects Sterling Control Center (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 Sterling Control Center

Vulnerability Details

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 plain text of encrypted connections.

CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 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 Sterling Control Center 5.4.2 through 5.4.2.1 iFix01
IBM Sterling Control Center 5.4.1 through 5.4.1.0 iFix02
IBM Sterling Control Center 5.4.0 through 5.4.0.1 iFix03
IBM Sterling Control Center 5.3 through 5.3.0.4 iFix02
IBM Sterling Control Center 5.2 through 5.2.12

Remediation/Fixes

Product

| VRMF|APAR|How to Acquire Fix
—|—|—|—
Sterling Control Center| 5.4.2.1
iFix03| N/A| 5.4.2.1 Fixes
Sterling Control Center| 5.4.1.0| N/A| Contact Support and request the latest 5.4.1.0 build fix package to be published for you on the ECuRep server.
Sterling Control Center| 5.4.0.1| N/A| Contact Support and request the latest 5.4.0.1 build fix package to be published for you on the ECuRep server.
Sterling Control Center| 5.3.04| N/A| Contact Support and request the latest 5.3 build fix package to be published for you on the ECuRep server.
Sterling Control Center| 5.2.12| N/A| Contact Support and request the latest 5.2 build fix package to be published for you on the ECuRep server.

Procedures to Disable SSLv3 for Sterling Control Center Secure Connections

Engine <-–> Classic GUI Console:
5.4.2.1 - Uncomment this line in the install-dir/conf/engine.properties file: com.ibm.jsse2.overrideDefaultProtocol=TLS
5.4.0 and 5.4.1 - Add this line in the install-dir/conf/engine.properties file, com.ibm.jsse2.overrideDefaultProtocol=TLS
5.2 and 5.3 - Add this property in the runEngine.bat|sh startup script -Dcom.ibm.jsse2.overrideDefaultProtocol=TLS

Web Server <-–> browser (web UI):
5.4.2.1 - Uncomment this line in the install-dir/conf/engine.properties file: WEBSERVER_SECURE_PROTOCOL=TLS
5.4.0 and 5.4.1 - Add this line in the install-dir/conf/engine.properties file: WEBSERVER_SECURE_PROTOCOL=TLS
5.2 and 5.3 - Add this property In the runEngine.bat|sh startup script -DWEBSERVER_SECURE_PROTOCOL=TLS

Connect:Direct Browser Node Properties:
Set the Protocol radio button to TLS or other non-SSL value

Monitored Connect:Direct Servers:
Disable SSLv3 in the SCC GUI (select TLS in the Server Connections tab)

Monitored Sterling Integrator Servers:
Disable SSLv3 on the SI Server SCC InterOp adapter connection.

Database Connections:
Disable SSLv3 on the database server.

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. You should verify disabling SSLv3 does not cause any compatibility issues.

Workarounds and Mitigations

None.