Security Bulletin: Vulnerability in SSLv3 affects IBM Sterling Connect:Direct FTP+ (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 by default in Connect:Direct FTP+.

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 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

IBM Sterling Connect:Direct FTP+ 1.3.0
IBM Sterling Connect:Direct FTP+ 1.2.0
IBM Sterling Connect:Direct FTP+ 1.1.0

Remediation/Fixes

V.R.M

| APAR|Remediation
—|—|—
1.3.0| IT07069| Apply 1.3.0.0.iFix001, available on Fix Central
1.2.0| IT07069| Apply 1.2.0.0.iFix006, available on Fix Central
1.1.0| IT07069| Apply 1.1.15 Fix 10, available on IWM
This fix changes the default protocol when creating a new configuration entry from SSLv3 to TLS.

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.

Workarounds and Mitigations

Disable SSLv3 in existing configuration entries in Connect:Direct (C:D) FTP+:

1. Start the Connect:Direct FTP+ configuration interface. See the “IBM Sterling Connect:Direct FTP+ Configuration Guide” for details.
2. For each configuration listed, review the C:D FTP+ tab:

• If “Use Secure+ for transfers?” is set to No, the configuration is not vulnerable.
• If “Use Secure+ for transfers?” is set to Yes and “Use Secure+ SSL protocol (otherwise, TLS)” is set to No, the configuration is not vulnerable.
• If “Use Secure+ for transfers?” is set to Yes and “Use Secure+ SSL protocol (otherwise, TLS)” is set to Yes, edit the configuration and set “Use Secure+ SSL protocol (otherwise, TLS)” to No to mitigate the vulnerability.