Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2015.1154
Security Bulletin: Vulnerability in RC4 stream cipher affects IBM FileNet
Content Manager, IBM FileNet BPM and IBM Content Foundation
products (CVE-2015-2808)
28 April 2015
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM FileNet Content Manager
Publisher: IBM
Operating System: AIX
Linux variants
Solaris
Windows
Impact/Access: Access Privileged Data -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2015-2808
Reference: ESB-2015.1150
ESB-2015.1149
ESB-2015.1148
ESB-2015.1147
ESB-2015.1143
ESB-2015.1141
Original Bulletin:
http://www-01.ibm.com/support/docview.wss?uid=swg21701597
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: Vulnerability in RC4 stream cipher affects IBM FileNet
Content Manager, IBM FileNet BPM and IBM Content Foundation products
(CVE-2015-2808)
Security Bulletin
Summary
The RC4 Bar Mitzvah Attack affects products that use the SSL/TLS protocol as a
means for secure communication. The IBM FileNet Content Manager, IBM FileNet
BPM and IBM Content Foundation products can be configured to use the SSL/TLS
protocol and are thus potentially affected by this attack. If using the
SSL/TLS protocol with these products, please refer to the sections below to
remediate this security vulnerability.
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 FileNet Content Manager 5.0.0, 5.1.0, 5.2.0, 5.2.1 (CSS)
IBM Content Foundation 5.2.0, 5.2.1 (CSS)
IBM FileNet BPM 4.5.1, 5.0.0
Remediation/Fixes
The RC4 Bar Mitzvah Attack can be remediated by upgrading to Java Runtime
Environment (JRE) v1.6.0 SR16 FP3 + IV70681 + IV71888 or higher. By installing
the applicable fixes in the table below, the private IBM JRE used by Process
Engine and Content Platform Engine will be updated to resolve the security
vulnerability.
Product VRMF APAR Remediation/First Fix Available
FileNet Content Manager (FNCM) 4.5.1 PJ43167 5.1.0.0-P8CSS-IF012 - 4/27/2015
5.0.0 PJ43169 5.2.0.2-P8CSS-IF004 - 4/27/2015
5.1.0 5.2.1.0-P8CSS-IF002 - 4/27/2015
5.2.0
5.2.1
IBM Content Foundation (ICF) 5.2.0 PJ43167 5.2.0.2-P8CSS-IF004 - 4/27/2015
5.2.1 PJ43169 5.2.1.0-P8CSS-IF002 - 4/27/2015
FileNet BPM (FBPM) 4.5.1 n/a
5.0.0
IBM recommends that you review your entire environment to identify other areas
where you have enabled the RC4 stream cipher (associated with the SSL/TLS
protocols) and take appropriate mitigation and remediation actions.
Workarounds and Mitigations
You should verify that applying the configuration changes recommended below
does not cause any compatibility issues.
Mitigation is to disable RC4:
Web application administrators should disable RC4 in their application's
TLS configuration on the application server.
Web users are encouraged to disable RC4 in their browser's TLS
configuration.
Case Foundation 5.2.1 / CPE 5.2.1
or
Case Foundation 5.2.0 / CPE 5.2.0
If using the legacy Component Manager you should do either of the
following:
Configure the legacy Component Manager so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line for your legacy
component. This is done with the Process Task Manager on the server where the
legacy Component Manager is running.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any legacy Component
Managers are using that JRE.
On the Content Platform Engine (CPE) Server, the Java Runtime Environment
(JRE) is not supplied by the FileNet Content Manager, IBM Content Foundation
or FileNet BPM software. The mitigation on the CPE Server side comes from the
supplier of your JRE or from the application server being used to host the CPE
Server software.
For Java based Content Engine system tools (such as FileNet Deployment
Manager (FDM) and Content Engine Bulk Import Tool (CEBIT)), you should do
either of the following:
Configure each tool so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line that initiates
the tool.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any Java based
Content Engine system tool is using that JRE.
On the Content Platform Engine Client side, the Java Runtime Environment
(JRE) is not supplied by the FileNet Content Manager, IBM Content Foundation
or FileNet BPM software. The mitigation on the CPE Client side comes from the
supplier of your JRE or from the application server being used to host the
Content or Case Foundation applications.
Process Engine 5.0 (PE 5.0)
On the PE Server, configure the PE software so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line.
For example:
Stop the PE Server software
Edit the .../IBM/FileNet/ProcessEngine/startpesvr.bat file (on Windows
servers) or the startpesvr script (on Unix or Linux servers) and add
-Dcom.ibm.jsse2.JSSEFIPS=true so that the java command in the batch/script
file begins like this:
"%JAVA_HOME%\bin\java" -Dcom.ibm.jsse2.JSSEFIPS=true
-Djpeserver.useHTTPTunneling=false ...
Start the PE Server software
For the Component Manager, you should do either of the following:
Configure the Component Manager so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line for running the
component. This is done with the Process Task Manager on the server where the
Component Manger is running.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any Component
Managers are using that JRE.
On the Process Engine Client side, the Java Runtime Environment (JRE) is
not supplied by the FileNet BPM software. The mitigation on the PE Client side
comes from the supplier of your JRE used to run your PE applications.
Process Engine 4.5.1 (PE 4.5.1)
For the Component Manager, you should do either of the following:
Configure the Component Manager so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line for running the
component. This is done with the Process Task Manager on the server where the
Component Manger is running.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any Component
Managers are using that JRE.
On the Process Engine Client side, the Java Runtime Environment (JRE) is
not supplied by the FileNet BPM software. The mitigation on the PE Client side
comes from the supplier of your JRE used to run your PE applications.
eProcess 5.2.0
For the Component Manager, you should do either of the following:
Configure the Component Manager so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line for running the
component. This is done with the Process Task Manager on the server where the
Component Manger is running.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any Component
Managers are using that JRE.
On the eProcess Client side, the Java Runtime Environment (JRE) is not
supplied by the FileNet BPM software. The mitigation on the eProcess Client
side comes from the supplier of your JRE used to run your eProcess
applications.
Content Federation Services
For Content Federation Services installation:
Content Federation Services (CFS) uses the Content Engine/Content Platform
Engine (CE/CPE) Client Download API during installation. You should do all of
the following for 5.2.0.2-CFS-FP002 and prior:
Make sure the "Bar Mitzvah" issue is addressed on the CPE server
before launching the Content Federation Services (CFS) installer.
Get a Java Runtime Environment (JRE) that includes a fix for the Bar
Mitzvah issue (if one is available) and launch the CFS installer program with
this JRE.
The command syntax is:
<Executable file name for CFS installer> LAX_VM <Java executable>
For example:
(Windows)
5.1.0-CFS-WIN.EXE LAX_VM
C:\Program Files (x86)\Java\NEW_JRE\bin\java.exe
(UNIX)
./5.1.0-CFS-<PLATFORM>.BIN LAX_VM /opt/NEW_JRE/jre/bin/java
For Content Federation Services Federation Administration application:
At the application server where Content Federated Services Federation
Administration is deployed, apply the mitigations from the application server
provider.
Content Engine tools 5.0.0, 5.1.0, 5.2.0, 5.2.1
For Java based Content Engine system tools (such as FileNet Deployment
Manager (FDM) and Content Engine Bulk Import Tool (CEBIT)), you should do
either of the following:
Configure each tool so that it is invoked with the
-Dcom.ibm.jsse2.JSSEFIPS=true option on the java command line that initiates
the tool.
or
Obtain a Java Runtime Environment (JRE) that includes the fix for the
"Bar Mitzvah" issue (if one is available) and ensure that any Java based
Content Engine system tool is using that JRE.
Content Engine Client Download API
At the application server where Content Engine Client Downloader API is
deployed, apply the mitigations from the application server provider.
For httpsURLConnection, set the https.cipherSuites system property to not
include the RC4 cipher suites.
Application Server Notes
How to disable RC4 for WebSphere:
http://www.ibm.com/support/docview.wss?uid=swg21701503
How to disable RC4 for JBoss:
Contact your provider for the instructions on how to disable RC4.
How to disable RC4 for WebLogic:
Contact your provider for the instructions on how to disable RC4.
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
16 April 2015: Original Version Published
27 April 2015: Content Search Services interim fixes released
*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
iQIVAwUBVT8XPxLndAQH1ShLAQKlXw/+J32fBqjw4ZDbw8DIouwHunHVjuLMNU9Q
ZfwAe0+iyAwDD7AAIZ+Pe+lbwcRZ5horTd/Kr7RWOMOf9XijYl+Gsx39qtrzfikK
4FKSvmE73xNfyuoVbRyPVK4+K8mDFhwKILOA7MCG8f1BXoFrxICB+j7E7e6l3oi6
AzNw8SOpJNJFWp7sMUEYWdDsHgM8tWkC8EMscp9SVzkWEqxF3A6fzJDaHl/7XW8p
usdkMwqzHd7n8t6pQwW5CmFXdSJNPJ7Q956AIcgU2u6K93XPrcTTdBdYs67mERXU
7KeOmQ2eiARQxr7r6+KjiFhhx5iLhA03+NosXJC9Ue3d1kGxYihNceL0N7sun+tL
wpqm5EX+G9JFkfCXghBPssRCZi1SeqhFIOBGYGNCUo+pYX/SnRBWFjqAJnpGxC5w
uTpTel6mY9TfGmqJLeRXpRrQjoEbkJdlFawZBx2OS11+naeZbmYXWuDw4DQBainl
PKBUOIwebzONnkcWQ/qVnVZJbw9sspabHqn6vCvfULmSq9htx44Ae3qIytjCR8/F
whftrAe7uH2ByD4v+qHyGwClyp/xhdp+hk746un6orTQKP1NWy6bCyuKZmemSzNR
6uOCBGQGu04T53x9xs5W80qVz96A6vEBCM287FZtvGm/x1wJ/cIMUIWNZ8r0twsj
divXXNQiBqs=
=N7pY
-----END PGP SIGNATURE-----