-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2016.0668
         Security Bulletin: "SLOTH" vulnerability in IBM Java SDK
                affects InfoSphere Streams (CVE-2015-7575)
                               11 March 2016

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           IBM InfoSphere Streams
Publisher:         IBM
Operating System:  Linux variants
Impact/Access:     Access Privileged Data         -- Remote with User Interaction
                   Provide Misleading Information -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2015-7575  

Reference:         ASB-2016.0004
                   ESB-2016.0643
                   ESB-2016.0607
                   ESB-2016.0585
                   ESB-2016.0574
                   ESB-2016.0570
                   ESB-2016.0556

Original Bulletin: 
   http://www.ibm.com/support/docview.wss?uid=swg21977838

- --------------------------BEGIN INCLUDED TEXT--------------------

Security Bulletin: "SLOTH" vulnerability in IBM Java SDK affects InfoSphere 
Streams (CVE-2015-7575)

Document information

More support for:

IBM Streams

Software version:

1.2, 2.0, 3.0, 3.1, 3.2, 3.2.1, 4.0, 4.0.1, 4.1

Operating system(s):

Linux

Software edition:

All Editions

Reference #:

1977838

Modified date:

2016-03-10

Security Bulletin

Summary

There is a vulnerability in IBM SDK Java Technology Edition, Versions 7R1 
Service Refresh 3 Fix Pack 1 and earlier releases and Version 8 Service 
Refresh 1 Fix Pack 1 and earlier releases that is used by IBM InfoSphere 
Streams. This vulnerability, commonly referred to as SLOTH, was disclosed as 
part of the IBM Java SDK updates in January 2016.

Vulnerability Details

CVEID: CVE-2015-7575

DESCRIPTION: The TLS protocol could allow weaker than expected security caused
by a collision attack when using the MD5 hash function for signing a 
ServerKeyExchange message during a TLS handshake. An attacker could exploit 
this vulnerability using man-in-the-middle techniques to impersonate a TLS 
server and obtain credentials. This vulnerability is commonly referred to as 
SLOTH.

CVSS Base Score: 7.1

CVSS Temporal Score: See 
https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 for the current 
score

CVSS Environmental Score*: Undefined

CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/UI:U/C:H/I:L/A:N)

Affected Products and Versions

  1.2.1.0

  2.0.0.4 and earlier

  3.0.0.5 and earlier

  3.1.0.7 and earlier

  3.2.1.4 and earlier

  4.0.1.1 and earlier

  4.1

Remediation/Fixes

Java technology is used for SSL/TLS in InfoSphere Streams. The "SLOTH" 
vulnerability in Streams can be corrected by applying the appropriate 
remediation or upgrade documented below.

NOTE: Fix packs are available on IBM Fix Central.

  Version 4.1. Take one of the following actions:

   Perform the mitigation steps for Java referenced in the Workarounds and 
   Mitigations section below.

   Upgrade to InfoSphere Streams Mod Release 4.1.1 (available on Passport 
   Advantage).

  Version 4.0.1: Perform the mitigation steps for Java referenced in the 
  Workarounds and Mitigations section below.

  Version 3.2.1: Perform the mitigation steps for Java referenced in the 
  Workarounds and Mitigations section below.

  Version 3.1.0: Contact Technical Support.

  Version 3.0.0: Contact Technical Support.

  Versions 1.2 and 2.0: For version 1.x and 2.x IBM recommends upgrading to a 
  fixed, supported version/release/platform of the product. Customers who cannot
  upgrade and need to secure their installation should open a PMR with IBM 
  Technical Support and request assistance securing their InfoSphere Streams 
  system against the vulnerabilities identified in this Security Bulletin.

IMPORTANT NOTE: If JAVA_HOME is set ensure it points to the install location 
of the upgraded IBM Developer Kit, Java. Applications compiled with JAVA_HOME
set to a different location will need to be recompiled after JAVA_HOME has 
been changed. For more information on compiling with JAVA_HOME set see the 
Notes section on the page at this URL: 
http://www-01.ibm.com/support/knowledgecenter/SSCRJU_4.0.0/com.ibm.streams.install.doc/doc/ibminfospherestreams-install-prerequisites-java-supported-sdks.html?lang=en

Workarounds and Mitigations

Customers using Streams versions 3.2.1, 4.0.1, or 4.1 should disable the use 
of the MD5 hash by editing the java.security file and adding or updating the 
entry for the jdk.certpath.disabledAlgorithms property with "MD5" and adding 
or updating the entry for the jdk.tls.disabledAlgorithms property with 
"MD5withRSA". If the documented mitigation for the "SLOTH" vulnerability has 
previously been applied, the java.security file will have entries similar to:

jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024, MD5

jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768, MD5withRSA

The java.security file is located in <STREAMS_INSTALL>/java/jre/lib/security.
Be certain that the line is not commented (does not begin with the "#" 
symbol).

Restart all domains and instances for this change to take effect. You should 
verify applying this configuration change does not cause any compatibility 
issues. Not disabling the MD5 signature hash will expose yourself to the 
attack described above.

IBM recommends that you review your entire environment to identify other areas
where you have enabled the MD5 signature hash and take appropriate mitigation
and remediation actions.

Get Notified about Future Security Bulletins

Subscribe to My Notifications to be notified of important product support 
alerts like this.

References

Complete CVSS v3 Guide

On-line Calculator v3

Related information

IBM Secure Engineering Web Portal

IBM Product Security Incident Response Blog

Change History

11 March 2016: Original version published

*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

iQIVAwUBVuIdWX6ZAP0PgtI9AQJ21A//fm7BePtJuCive3gCVE1mJFKrzFS4Nfha
0w6Py5tcvPUfD9srnIYw0SUE3h8RMQn/xxPa+mUMRzbu2D2xc5b2t2jJ3w4ZWIHa
bAXZaZnjO0p2+LzDsbEXw+ijAn5VjdBtojHArlvCzViT7303Z0BUh5zkpmhkR6bF
/eL8PaQSNHcHf1KI4bWf76XuYGVv1afrNyHqF0OQO4GCuZ21sCielNyNVEKIDnO6
rcnlhAVMGMVBUSmkdhjxECY/vpnp3SUHPjWAlwJ9ZErSr9qpyyMBiOA94xXsHlWG
ejUOLryazFEPZ5mvdA9VlLfD/dewsbi3eSTes1K+MhZqCsNcqYQ5ir3OC+q3mttD
LZYEftzC8MJUdNaxWPdEFzp9Yr+FYbEEmWscB1rvogIocQlLgWMrshJNRA/AkUK/
UolBjeqqCdvYwXj6N6WB0UKUnqbeXCNNcanPcrVB8bnxZeZe3IhHu0yd51wcZJcq
PZq5qkEnliGb2tNSZ1BmKzMlShM+Oar8AOLAIpHrPz7tqW0BXz3lDtgNX6Hw+1ya
0JUiKpzIO/X0RX4FmMW82z5OYizZkllzgnzIqodsLDq0Mev4ZBCSVSZLpzxlm49W
+01jRBYuwlHH+hWXnzXggs5u/LiWMcx20/V8ylbS1GrPptLl/XWq9EDiAS3ntYkf
JsDkWoF7P2I=
=7GBf
-----END PGP SIGNATURE-----