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 IBM WebSphere Application Server. These fixes will disable SSLv3 completely.
Vulnerability Details
CVE ID: CVE-2014-3566
DESCRIPTION: IBM WebSphere Application 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)
Affected Products and Versions
This vulnerability affects all versions and releases of IBM WebSphere Application Server, IBM WebSphere Application Server Full Profile, IBM WebSphere Application Server Liberty Profile and IBM WebSphere Application Server Hypervisor Edition.
Remediation/Fixes
Please refer to the Security Bulletin for IBM HTTP Server to remediate your webserver.
Please note that these fixes will remove SSLv3 completely.
If you have SSL hard coded in your application code, such as SSLContext.getInstance("SSL") then you should install the interim fixes listed below since the current implementation defaults that context to SSLv3. The interim fix is an enhancement in the IBM JDK.
The following table lists some common standard protocol label names for Java 5 and above:
Protocol | Prior to this fix | After this fix |
SSL | SSL v3.0 | see chart below |
SSLv3 | SSL v3.0 | Connection will fail |
TLS | TLS v1.0 (defined in RFC 2246) | TLS v1.0 (defined in RFC 2246) |
TLSv1 | TLS v1.0 (defined in RFC 2246) | TLS v1.0 (defined in RFC 2246) |
TLSv1.1 | TLS v1.1 (defined in RFC 4346) | TLS v1.1 (defined in RFC 4346) (not available for version 6.1) |
TLSv1.2 | TLS v1.2 (defined in RFC 5246) | TLS v1.2 (defined in RFC 5246) (not available for version 6.1) |
SSL_TLS | Enables all SSL V3.0 and TLS 1.0 protocols | TLS 1.0 |
SSL_TLSv2 | Enables all SSL V3.0 and TLS 1.0, 1.1 and 1.2 protocols | TLS 1.0, 1.1 and 1.2 protocols (not available for version 6.1 and for version 7.0 only available with fix pack 7.0.0.23 or later.) |
The IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server will be updated per the chart below, so that SSL Protocol alias label of "SSL" would mean the TLS levels marked.
Java Version | TLS 1.0 | TLS 1.1 | TLS 1.2 |
Java 7 Server | x | x | x |
Java 7 Client | x | ||
Java 6 | x | ||
Java 5 | x |
-Dcom.ibm.jsse2.disableSSLv3=false
Second, update the Oracle system property jdk.tls.disabledAlgorithms by removing SSLv3 from the list. This property is defined in the java.security file and any protocols in this list will be disabled. You can modify the setting to remove SSLv3 or add further algorithms with the following syntax:
For the IBM SDK, Java Technology Edition that is used by IBM WebSphere Application Server Full Profile:
For Java 7 or Java 8:
- Edit the java.security file and turn off SSLv3 by adding: jdk.tls.disabledAlgorithms=SSLv3
For the IBM SDK, Java Technology Edition or Oracle Java SDK, that is used by IBM WebSphere Application Server Liberty Profile:
- Edit the java.security file and turn off SSLv3 by adding: jdk.tls.disabledAlgorithms=SSLv3
This security property has precedence over the IBM system property com.ibm.jsse2.disableSSLv3
Please refer to the knowledge center for more information: http://www-01.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.security.component.70.doc/security-component/jsse2Docs/disablesslv3.html?lang=en
For IBM WebSphere Application Server and IBM WebSphere Application Server Hypervisor Edition :
If using Installation Manager 1.7.3.1 or older, please refer to the reference section and upgrade to Installation Manager 1.8 or newer.
Download and apply the interim fix APARs below, for your appropriate release:
For V8.5.0.0 through 8.5.5.3 Full Profile and Liberty Profile IM install:
- Apply Interim Fix PI28435: Will upgrade you to IBM Java SDK Version 7R1 Service Refresh 1 Fix Pack 1 (optional) + APAR IV66110 for change to disable SSLv3 by default
- Apply Interim Fix PI28436: Will upgrade you to IBM Java SDK Version 7 Service Refresh 7 Fix Pack 1 (optional) + APAR IV66110 for change to disable SSLv3 by default
- Apply Interim Fix PI28437: Will upgrade you to IBM Java SDK Version 6R1 Service Refresh 8 Fix Pack 1 (required) + APAR IV66110 for change to disable SSLv3 by default
- Apply IBM Java SDK shipped with the WebSphere Application Server Fix pack 8.5.5.4 or later.
For 8.0.0.0 through 8.0.0.9:
- Apply Interim Fix PI28438: Will upgrade you to IBM Java SDK Version 6R1 Service Refresh 8 Fix Pack 1 + APAR IV66110 for change to disable SSLv3 by default
- Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 10 (8.0.0.10) or later.
For V7.0.0.0 through 7.0.0.35:
- Apply Interim Fix PI28439: Will upgrade you to IBM Java SDK Version 6 Service Refresh 16 Fix Pack 1 + APAR IV66110 for change to disable SSLv3 by default
- Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 37 (7.0.0.37) or later.
For V6.1.0.0 through 6.1.0.47:
- Apply Interim Fix PI28796 : Will upgrade you to IBM Java SDK Version 5.0 Service Refresh 16 Fix Pack 7 + APAR IV66111 for change to disable SSLv3 by default.
For IBM WebSphere Application Server Liberty Profile not using IM install
Please refer to the vendor that supplies you SDK. For users of the IBM SDK, Java Technology Edition please refer to this security bulletin: IBM SDK, Java Technology Edition fixes to mitigate against the POODLE security vulnerability
For IBM WebSphere Application Server for i5/OS operating systems:
The IBM Developer Kit for Java is prerequisite software for WebSphere Application Server for IBM i. Please refer to Java on IBM i for updates on when these fixes will be available.
Workarounds and Mitigations
None. Please apply Interim Fix or Fix Packs.
IBM recommends that you review your entire environment to identify other areas that enable SSLv3 protocol and take appropriate mitigation (such as disabling SSLv3) and remediation actions.
Get Notified about Future Security Bulletins
Important Note
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
References
Product updates not found when using IBM Installation Manager 1.7.3.1 or older
HTTPS advisor fails when SSLv3 is disabled on backend servers
IBM SDK, Java Technology Edition fixes to mitigate against the POODLE security vulnerability
Change History
15 October 2014: original document published
20 October 2014: fix quote in wrong location for wsadmin command
22 October 2014: clarified SSL_TLS versus TLS
31 October 2014: added ifixes for remediation
6 November 2014: added link to version 6.1 ifix
20 November 2014: bolded note about when to restart the server
2 December 2014: added link in reference section
2 February 2015: updated APAR number typo
5 March 2015: updated Mitigation section
30 March 2015: added link to Setting JVM properties
30 March 2015: added links for Liberty profile
6 May 2015: updated protocol table, added Warnings
26 October 2015: clarified java.security updates
*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.
Was this topic helpful?
Document Information
Modified date:
07 September 2022
UID
swg21687173