IBM Support

Security Bulletin: Vulnerability in SSLv3 affects IBM Sterling B2B Integrator and IBM Sterling File Gateway (CVE-2014-3566)

Created by Philip J Ross on
Published URL:
https://www.ibm.com/support/pages/node/517765
517765

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 in IBM Sterling B2B Integrator.

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 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)

Warning: We strongly encourage you to take action as soon as possible as potential implications to your environment may be more serious than indicated by the CVSS score.

Affected Products and Versions

IBM Sterling B2B Integrator 5.2

IBM Sterling File Gateway 2.2

Sterling Integrator 5.1

Sterling File Gateway 2.1

Remediation/Fixes

Product & Version

APAR
Remediated Fix
Sterling Integrator 5.1 or Sterling File Gateway 2.1IT05094Apply Generic Interim Fix 5104_6. Available on IWM
IBM Sterling B2B Integrator 5.2 or IBM Sterling File Gateway 2.2IT05094,IT05211Install 5020500 Media or apply 5020500 FixPack that is made available on Passport Advantage and Fix Central respectively

To acquire the fix please login to IBM Fix Central
More details and release notes can be found here:
IBM Sterling B2B Integrator 5.2 Information Center

To acquire the fix from Passport Advantage, please login here.

To acquire the fix from IWM, please login here.

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

Reconfigure to disable SSLv3 and select TLS 1.0 or higher where possible. If using NIST strict mode, TLS 1.2 is already enabled.

The following table provides instructions on how to reconfigure secure connection settings that apply to both Sterling B2B Integrator 5.2 and 5.1, except where noted. After making the necessary changes, you will need to stop and restart IBM Sterling B2B Integrator in order for these changes to take affect.

If you use:Then do this:
  • Dashboard
  • Map Editor
  • All other product UIs
Disable SSLv3 in your internet browser. See your internet browser help for instructions on how to do this.
  • Communications adapters (FTP Client, FTP Server, HTTP Client, HTTP Server etc.)
  • Sterling Control Center Monitor
  • SWIFTNet Server adapter

    Note that these instructions help to disable SSLv3 for HTTP Server Adapter in fixpack 5103 onwards and 5.2.4.1 onwards. Those who are on older fixpacks need to upgrade to latest versions to apply the fix to HTTP Server Adapter.
  1. Navigate to the installation directory
  2. Navigate to the properties directory.
  3. Edit the customer_overrides.properties file.
  4. Add security.SSLHelloProtocol=TLS1-TLS1.2 to the end of the file.
    Note: If you already have security.SSLHelloProtocolForFIPS=TLS1-ONLY in customer_overrides.properties, keep this default value.
  5. Save and close the file.
  • JMS1.1 Acquire Connection and Session service
  • JMS1.1 Async Receive adapter
Disable SSLv3 in your JMS server. See your JMS server documentation for information on how to do this.
  • SMTP Send adapter
  • B2B Mail Client adapter
Disable SSLv3 in your mail server. See your mail server documentation for information on how to do this.
  • WebSphere MQ Suite Async Receive adapter
  • WebSphere MQ adapter
  • WebSphere MQ File Transfer Edition Agent adapter (Sterling B2B Integrator 5.2 only)
  • WebSphere MQ File Transfer Edition Create Transfer service (Sterling B2B Integrator 5.2 only)
  • MEIG Messaging Config adapter (Applies only to Multi-Enterprise Integration Gateway users of Sterling B2B Integrator 5.2.4.2)
Disable SSLv3 in your MQ server. See your WebSphere MQ server documentation for information on how to do this.

When using these adapters, only use TLS ciphers. For more information, see the WSMQ security bulletin:
Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere MQ, IBM WebSphere MQ Internet Pass-Thru and IBM Mobile Messaging and M2M Client Pack (CVE-2014-3566)
  • Connect:Direct Requester Adapter
  • Connect:Direct Server Adapter
Update all existing configurations of these services and adapters to use TLS instead of SSL:
  1. Navigate to Deployment > Services > Configuration.
  2. Under List, select the service type you want to update and click Go!
  3. Click edit next to the service configuration you want to update.
  4. Click Next until you get to the Encryption screen.
  5. On the Encryption screen, under Encryption using Secure+, select Enabled and click Next.
  6. Complete the Secure+ Configuration screen as required, but in particular ensure that you select TLS under SSL or TLS for Sterling B2B Integrator version before 5.2.4.2 and select TLS 1.0 or TLS 1.2 under Security Protocol for version 5.2.4.2 and click Next.
  7. Click Finish.
  • OdetteFTP adapter (Sterling B2B Integrator 5.2.4.2 only)
  1. Navigate to the installation directory.
  2. Navigate to the properties directory.
  3. View the OdetteFTP.properties file.
  4. If you already have OFTP.Global.HelloProtocol=TLS1-TLS1.2 keep this default value.
  5. If you do not have the default value, navigate to the customer_overrides.properties
  6. Edit the file and add
    OdetteFTP.OFTP.Global.HelloProtocol=TLS1-TLS1.2
  7. Save and close the file.

Get Notified about Future Security Bulletins

References

Off

Acknowledgement

None

Change History

05 November 2014: Initial Release
05 December 2014: Updated Workarounds and Mitigations section
12 December 2014: Updated Remediation with 5020500 as one of the Fix
5 January 2015: Updated for release in 5104_6
6 January 2015: Changed naming convention for 5.1 and 2.1

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

Disclaimer

Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.

[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.2.4.2;5.2.4.1;5.2.4;5.2.3;5.2.2;5.2.1;5.2;5.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21688904