I received an email from IBM today and I’d like to pass along the security information. This came directly from IBM.

While this issue is not specifically with DataPower, DataPower can leverage SSLv3, so please ensure you’re assessing all of your security infrastructure leveraging SSLv3. Please take appropriate actions.


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

Security Bulletin 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 DataPower.Vulnerability Details:CVE-IDCVE-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 http://xforce.iss.net/xforce/xfdb/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 All DataPower products and versions that have configured a DataPower Crypto Profile object for SSL communication.

Remediation/Fixes None

Workarounds and Mitigations Disable SSL v3 in DataPower configuration.

First make sure to Quiesce all domains and services to stop traffic to the appliance. System quiesce and unquiesce commands can be invoked by navigating to Administration –> Main –> System Control.

Next, select Objects –> Crypto Configuration –> Crypto Profile in the left navigation pane. For all the crypto profile objects that are configured, in the “Configure Crypto Profile” page, “Options” parameter, select the checkbox “Disable SSL version 3”. Click Apply.

Note that SSL v3 must be disabled in all the Crypto Profile objects configured in all the domains. IBM recommends that you review your entire environment to identify other areas that enable the SSLv3 protocol and take appropriate mitigation such as disabling SSLv3 and remediation actions.

Jon Storm began his media career in 1996 with Game Informer Magazine and never looked back. He went on to serve as lead and chief editor for several other national magazine titles and is now a senior content consultant at TxMQ. He makes his home in Fredonia, NY.

Pin It on Pinterest

Share This