Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2015.1267.2
Security Bulletin: Vulnerability in RC4 stream cipher
affects IBM Rational ClearCase (CVE-2015-2808)
25 June 2015
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM Rational ClearCase
Publisher: IBM
Operating System: AIX
HP-UX
Linux variants
Solaris
Windows
Impact/Access: Access Privileged Data -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2015-2808
Reference: ESB-2015.0962
ESB-2015.0961
ESB-2015.0960
ESB-2015.0958
ESB-2015.0956
ESB-2015.0955
ESB-2015.0954
ESB-2015.0953
ESB-2015.0950.2
ESB-2015.0949.2
ESB-2015.0948.2
ESB-2015.0947.2
ESB-2015.0946.2
ESB-2015.0944.2
Original Bulletin:
http://www-01.ibm.com/support/docview.wss?uid=swg21701583
Revision History: June 25 2015: Fix is now included in fix packs
May 11 2015: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: Vulnerability in RC4 stream cipher affects IBM Rational
ClearCase (CVE-2015-2808)
Document information
More support for:
Rational ClearCase
Software version:
7.1, 7.1.0.1, 7.1.0.2, 7.1.1, 7.1.1.1, 7.1.1.2, 7.1.1.3, 7.1.1.4, 7.1.1.5,
7.1.1.6, 7.1.1.7, 7.1.1.8, 7.1.1.9, 7.1.2, 7.1.2.1, 7.1.2.2, 7.1.2.3, 7.1.2.4,
7.1.2.5, 7.1.2.6, 7.1.2.7, 7.1.2.8, 7.1.2.9, 7.1.2.10, 7.1.2.11, 7.1.2.12,
7.1.2.13, 7.1.2.14, 7.1.2.15, 7.1.2.16, 7.1.2.17, 8.0, 8.0.0.1, 8.0.0.2,
8.0.0.3, 8.0.0.4, 8.0.0.5, 8.0.0.6, 8.0.0.7, 8.0.0.8, 8.0.0.9, 8.0.0.10,
8.0.0.11, 8.0.0.12, 8.0.0.13, 8.0.0.14, 8.0.1, 8.0.1.1, 8.0.1.2, 8.0.1.3,
8.0.1.4, 8.0.1.5, 8.0.1.6, 8.0.1.7
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows
Reference #:
1701583
Modified date:
2015-06-24
Security Bulletin
Summary
The RC4 Bar Mitzvah Attack for SSL/TLS affects IBM Rational ClearCase.
Vulnerability Details
CVEID: CVE-2015-2808
DESCRIPTION: The RC4 algorithm, as used in the TLS protocol and SSL protocol,
could allow a remote attacker to obtain sensitive information. An attacker
could exploit this vulnerability to remotely expose account credentials
without requiring an active man-in-the-middle session. Successful exploitation
could allow an attacker to retrieve credit card data or other sensitive
information. This vulnerability is commonly referred to as "Bar Mitzvah
Attack".
CVSS Base Score: 5
CVSS Temporal Score: See
https://exchange.xforce.ibmcloud.com/vulnerabilities/101851 for the current
score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
Affected Products and Versions
IBM Rational ClearCase, versions 7.1.0.x, 7.1.1.x, 7.1.2.x, 8.0.0.x, 8.0.1.x,
in the following components:
CCRC WAN server/CM Server component, when configured to use SSL (all
platforms)
Base CC/CQ V2 (Perl trigger-based) integration, when configured to use SSL to
communicate with a ClearQuest Web server (all platforms)
CMI and OSLC integrations, including UCM/ClearQuest integration via OSLC
(UNIX/Linux platforms), when configured to use SSL. (Windows CMI/OSLC clients
are not affected in the default configuration.)
CMI/OSLC integration clients (Windows) and automatic view client (Windows),
when SSLv3 is enabled (not the default configuration)
ClearCase remote client: CCRC/CTE GUI, rcleartool, and CMAPI clients, when
using SSL to access a CCRC WAN Server/CM Server
Customer defined uses of SSL from ratlperl scripts
Remediation/Fixes
All fixes listed below except CCRC WAN server/CM server require the latest
published fix pack before applying the rest of the fix.
Affected Versions Applying the fix
8.0.1 through 8.0.1.7 Install Rational ClearCase Fix Pack 8 (8.0.1.8) for 8.0.1
8.0 through 8.0.0.14 Install Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
7.1.2 through 7.1.2.17 Customers on extended support contracts should install
Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2
7.1.1.x (all fix packs)
7.1.0.x (all fix packs)
CCRC WAN server/CM Server component:
The solution is to apply fixes or mitigations to your WAS and IHS components.
If your clients connect to IHS via SSL (which then redirects their connections
to WAS), then review this IHS bulletin: Security Bulletin: Vulnerability in
RC4 stream cipher affects IBM HTTP Server (CVE-2015-2808) and apply fixes or
remediations to your server.
If your clients connect directly to WAS with SSL, then review this bulletin
for instructions on applying a mitigation or fix to your WAS installation and
your ClearCase profile:
Security Bulletin: Vulnerability in RC4 stream cipher affects WebSphere
Application Server (CVE-2015-2808).
Depending on your version of ClearCase, you may need additional steps when
installing IHS or WAS fixes:
Affected Versions Applying the fix
7.1.0.x, 7.1.1.x, and 7.1.2.x Document 1390803 explains how to update
WebSphere Application Server and/or IBM HTTP
Server for ClearCase CM Servers at release 7.1.x.
Consult those instructions when applying the fix.
8.0.0.x
8.0.1.x Apply the appropriate WebSphere Application Server
and/or IBM HTTP Server fix directly to your CCRC
WAN server host. No ClearCase-specific steps are
necessary.
Base CC/CQ Perl trigger-based (V2) integration:
CMI and OSLC change management integrations (UNIX/Linux platforms):
The solution is to update to the fix pack listed above.
CMI/OSLC integration clients (Windows) and automatic view client (Windows),
when SSLv3 is enabled
The solution is to update to the fix pack listed above, then restore the
default configuration with SSLv3 disabled.
To disable SSLv3, remove the environment variable CCASE_ENABLE_SSLV3 from your
configuration. This is not a default configuration, and would only have been
set if you needed to temporarily enable SSLv3 support, which was disabled by
the fixes listed in Security Bulletin: Vulnerability in SSLv3 affects IBM
Rational ClearCase (CVE-2014-3566).
Customer defined uses of SSL from ratlperl scripts
The solution is to update to the fix pack listed above, then check and modify
your ratlperl scripts that use OpenSSL.
Disable any uses of the insecure RC4 cipher when you use IO::Socket::SSL. The
SSL_cipher_list setting configures permissible ciphers for use by OpenSSL .
You can view the documentation with:
ratlperl -e "use Pod::Perldoc; Pod::Perldoc->run();" IO::Socket::SSL
You can view the Base CC/CQ Perl trigger-based (V2) integration for an
example, in the script module <ccase-home-dir>/lib/CQCC/CQWebJavaParser.pm
ClearCase remote client: CCRC/CTE GUI, rcleartool, CMAPI clients
The solution is to update to the fix pack listed above.
Notes:
If you use CCRC as an extension offering installed into an Eclipse shell (one
not provided as part of a ClearCase release), or you use rcleartool or CMAPI
using a Java Virtual Machine not supplied by IBM as part of Rational
ClearCase, you should update the Java Virtual Machine you use to include a fix
for the above issues (disabling RC4 by default). Contact the supplier of your
Java Virtual Machine.
You should verify applying this fix does not cause any compatibility issues.
The fix disables RC4 stream cipher by default. If you change this setting you
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 RC4 stream cipher and take appropriate mitigation and remediation actions.
For unsupported versions, IBM recommends upgrading to a fixed, supported
version/release/platform of the product.
Workarounds and Mitigations
See above section.
Get Notified about Future Security Bulletins
Subscribe to My Notifications to be notified of important product support
alerts like this.
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
Complete CVSS Guide
On-line Calculator V2
Related information
IBM Secure Engineering Web Portal
IBM Product Security Incident Response Blog
Acknowledgement
None
Change History
* 8 May 2015: Original copy published.
* 24 June 2015: fix is now included in fix packs
*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
iQIVAwUBVYtYWn6ZAP0PgtI9AQLHng/9ECACwgp2ZWxrf3IlZvZSmn0hlfh0xBFe
/TPppPVGUJk+5Fx+S/VCA+bKgfggNSA51B6whwip9mIuR9UyFpeP4E1tUJP0EPmL
0+mWyrkONwEj+SDTht6XJVKQnvyp6ffuPjBGUcHPMy/wA8ywr16LpEMqW056/4jB
Wy5e84MtkZHanNr1yPlvI92aEGJimLqHZWnKh/F+p9Cv+xNu9CQzjGZ1hyqx96F3
oUFvrL8kYyXEZLmf71/jkaxgBxApWuKejWT7OtTbTJ9DMlbUyx9i/Egk8rxsWI7W
kFKYsC+fiYLYPxABmx5MBaEeW/3qN+c8abtc6nhhMlYnGJGovNpEABkIfbNhU5do
BY8yC2I+PEeT9yvuvB+/ZfElFoM8c3dDqr41sXpmquUwPauDNw0CUb7ZiZO6up2O
EO7BFJnUHE9UNQXE9Zg26JPAtCbuDn08KcTXVgQSIRvFjh7akePQ4EO1C1XYjdYc
q1V9xfjrInQYFOdrC3YVu2mYfngVMHhAWiS5dM3BkvMroKVrwkKkwZsac/z8SpYZ
ODO990d/ncXdRfHejdlPtYcqB8JH2osCIDZtZygPXVlE4wNcrrIIgPKZ74I8RgZp
jGfIUQEIVHVtugxyy1WpkWpNHR/yXZ9/nQrUemnTe3EQOlGgP5p2q3XTkptZFNcJ
UA2SLiEqEII=
=jUqI
-----END PGP SIGNATURE-----