Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2014.1992 Security Bulletin: Vulnerability in SSLv3 affects IBM TXSeries for Multiplatforms Version 7.1 and 8.1 (CVE-2014-3566) 29 October 2014 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: IBM TXSeries Publisher: IBM Operating System: AIX HP-UX Linux variants Solaris Windows Impact/Access: Access Confidential Data -- Remote with User Interaction Reduced Security -- Remote with User Interaction Resolution: Mitigation CVE Names: CVE-2014-3566 Reference: ASB-2014.0122 ESB-2014.1858 Original Bulletin: http://www-01.ibm.com/support/docview.wss?uid=swg21688408 - --------------------------BEGIN INCLUDED TEXT-------------------- Security Bulletin: Vulnerability in SSLv3 affects IBM TXSeries for Multiplatforms Version 7.1 and 8.1 (CVE-2014-3566) Security Bulletin Document information More support for: TXSeries Documentation Software version: 7.1, 8.1 Operating system(s): AIX, HP Itanium, HP-UX, Linux/x86, Solaris, Windows Reference #: 1688408 Modified date: 2014-10-28 Summary SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. The document describes disabling SSLv3 usage with TXSeries. 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 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 TXSeries for Multiplatforms V7.1, V8.1 Remediation/Fixes None Workarounds and Mitigations Disable SSL v3 as default when using TXSeries IPIC configuration with SSL. TXSeries for Multiplatforms provides an optional configurable capability to enable SSL for its IPIC communication protocol. In this scenario the default protocols which are enabled are SSL v3, TLS 1.0 and TLS 1.1. TXSeries V7.1.0.4 or higher will support disabling SSLV3 when it is configured with GSKit version 8.x. The instructions below provide guidance to disable SSL v3. TXSeries for Multiplatforms V7.1 If you are on TXSeries for Multiplatforms V7.1, you need to upgrade to Fixpack 4 or higher. Lower fix pack levels do not support disabling SSL v3. Steps to disable SSL v3 (TXSeries V7.1.0.4 or higher) 1. Stop the TXSeries region. 2. If you have not configured your region to use GSKit version 8.x, set the below variable in the regions environment file. CICS_GSKIT_VERSION=8 If your region is already configured with GSKit version 8.x then go to step 3. (By Default TXSeries 7.1 support GSKit version 7.x. Refer to the TXSeries infocenter for further configuration details.) 3. Set the below environment variable in the regions environment file. CICS_SP800_131MODE=SP800_131MODE 4. Restart the TXSeries region. Note: This setting will set TLS 1.2 protocol and disable SSL v3, so only the TLS protocols TLS 1.0, TLS 1.1 and TLS1.2 are enabled for communication. TXSeries for Multiplatforms V8.1 Steps to disable SSL v3 (TXSeries V8.1.0.0 or higher) 1. Stop the TXSeries region. 2. Set the below environment variable in the regions environment file CICS_SP800_131MODE=SP800_131MODE 3. Restart the TXSeries region. Note: This setting will set TLS 1.2 protocol as default and disable SSL v3, so only the TLS protocols TLS 1.0, TLS 1.1 and TLS 1.2 are enabled for communication. Setting this to SP800_131MODE will enforce TLS processing. Please refer to TXSeries infocenter for further details. Disable SSL v3 as default when using TXSeries Web Administration Console in HTTPS mode. TXSeries Web Administration console can be configured to run in HTTPS mode, In this mode the default value is set to SSL v3. The instructions below provide guidance to disable SSL v3 for TXSeries Web Administration Console when operating in HTTPS mode. TXSeries for Multiplatforms V7.1 TXSeries Web Administration Console runs on TXSeries Lightweight Infrastructure web server, The SSL configuration of light-weight infrastructure is controlled by the config.properties and webcontainer.properties files in the conf directory of <TXInstall-dir/wui>. The property com.ibm.ssl.protocol has to be updated to specify TLS as the protocol to be used Steps to disable SSL v3 on LWI webserver are as follows. config.properties The properties of interest in the config.properties file are as shown with the values: # SSL support com.ibm.pvc.webcontainer.ssl.configfile=../../conf/sslconfig com.ibm.pvc.webcontainer.port.secure=443 webcontainer.properties The properties of interest in the webcontainer.properties file are as shown with their values: com.ibm.ssl.keyStorePassword.443=[xor] 9MW08GTL+uut1b0\= com.ibm.ssl.clientAuthentication.443=false com.ibm.ssl.trustStorePassword.443=[xor] 9MW08GTL+uut1b0\= com.ibm.ssl.trustStore.443=../security/keystore/ibmjsse2.jts sslEnabled=true com.ibm.ssl.keyStore.443=../security/keystore/ibmjsse2.jks # Specifies the protocol to use com.ibm.ssl.protocol.443=TLS TXSeries for Multiplatforms V8.1 TXSeries Web Administration Console and Inbound SOAP support use IBM Websphere Application Server Liberty profile as the web server. The Liberty profile offer a minimal SSL configuration that allow a user to only provide a keystore configuration and the rest of the SSL information is filled in by the runtime. The minimal configuration may look like this in the server.xml file: <keyStore id="defaultKeyStore" password="yourPassword" /> A ssl element can be added so the default ssl configuration will not use SSLv3. The sslProtocol attribute in the ssl element defines what protocol is used, setting it to TLS will override the default. <ssl id="defaultSSLConfig" keyStoreRef="defaultKeyStore" sslProtocol="TLS" /> <keyStore id="defaultKeyStore" password="yourPassword" /> If using custom ssl configurations besides the minimal configuration the protocol element needs to be set for each ssl element that is in the server.xml file. For example <ssl id="myCustomSSLConfig" keyStoreRef="defaultKeyStore" trustStoreRef="defaultTrustStore" clientAuthentication="true" sslProtocol="TLS" /> 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. References Complete CVSS Guide On-line Calculator V2 Related information IBM Secure Engineering Web Portal IBM Product Security Incident Response Blog Acknowledgement None *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 According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. - --------------------------END INCLUDED TEXT-------------------- You have received this e-mail bulletin as a result of your organisation's registration with AusCERT. The mailing list you are subscribed to is maintained within your organisation, so if you do not wish to continue receiving these bulletins you should contact your local IT manager. If you do not know who that is, please send an email to auscert@auscert.org.au and we will forward your request to the appropriate person. NOTE: Third Party Rights This security bulletin is provided as a service to AusCERT's members. As AusCERT did not write the document quoted above, AusCERT has had no control over its content. The decision to follow or act on information or advice contained in this security bulletin is the responsibility of each user or organisation, and should be considered in accordance with your organisation's site policies and procedures. AusCERT takes no responsibility for consequences which may arise from following or acting on information or advice contained in this security bulletin. NOTE: This is only the original release of the security bulletin. It may not be updated when updates to the original are made. If downloading at a later date, it is recommended that the bulletin is retrieved directly from the author's website to ensure that the information is still current. Contact information for the authors of the original document is included in the Security Bulletin above. If you have any questions or need further information, please contact them directly. Previous advisories and external security bulletins can be retrieved from: http://www.auscert.org.au/render.html?cid=1980 =========================================================================== Australian Computer Emergency Response Team The University of Queensland Brisbane Qld 4072 Internet Email: auscert@auscert.org.au Facsimile: (07) 3365 7031 Telephone: (07) 3365 4417 (International: +61 7 3365 4417) AusCERT personnel answer during Queensland business hours which are GMT+10:00 (AEST). On call after hours for member emergencies only. =========================================================================== -----BEGIN PGP SIGNATURE----- Comment: http://www.auscert.org.au/render.html?it=1967 iQIVAwUBVFBsdxLndAQH1ShLAQI0Ww/+LJakmbIL7kQuMO/yTuHgBzToc5Bns6dG AN06wbVTY1UHUdt3Pi9UBrLdTz2e749djYoyQAxphIJUzBKXG7geDfjHsRR00NPm 9h5AFNUHwUVV2FSwgKEdjsKrCzqrUYcfotYLOkRQJaLtUuh9kna5iPlzd+NxKwsE BUBaThjnpeqgnsw8CqID67dUarhhM6cgq1p34BFHL787Qf/nN0hlRcoM7BKdGoWH ZAh/MxxsJBjWVFsGBUgiNtrV0sfqHnT2Qv3KI3u8GrPlKV4W2JkuQMq/K4Ut7dnD 4VlVHZ6y5ng3zw3c+dr1hNys7TvPPjXdNKaAKALiwaYFkbEzlasvWRC7h0UOsA70 JyIq+wUK/+UaVmXN2ls6OA/mFH1vSRSCLbRqlyL76kL3s2zgYB2Zt0IGLM3uNXZv XNtOoA+jeDvBDPOKR80Uam6hRUavMW+DBvSwoDKXuIOjPEeet4gZLPK4xDjgXaKz veHwnnDF/ShnwWpzD0+/uJHZx57I1EoK6LsEeVT/1b9W96H41EW2bVzPQ5MW0i4t cK2HUdAxAUWBY6XIx9LsR3CwyX7qOeyrjFGgf295K12QJHH+jkd9DbST5oytZ5g+ 2OiO+2Tzdh0rrsGi09jEDBgg3XIQeX6C5WkHF0WJL7UZqXGtWsVys3ocFax2N0XB hlDlNT0EYv0= =+/wt -----END PGP SIGNATURE-----