5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.003 Low
EPSS
Percentile
65.1%
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.
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)
IBM FileNet Content Manager 5.1.0, 5.2.0, 5.2.1
IBM Content Foundation 5.2.0, 5.2.1
IBM FileNet Business Process Manager 4.5.1, 5.0.0, 5.2.0
The RC4 “Bar Mitzvah” Attack can be remediated by upgrading to Java Runtime Environment (JRE) v1.6.0 SR16 FP3 + IV70681 + IV71888 or higher, which is provided in the following releases in the table below.
Product | VRMF | APAR | Remediation/First Fix Available |
---|---|---|---|
FileNet Content Manager | 5.1.0 | ||
5.2.0 | |||
5.2.1 | PJ43167 | ||
PJ43169 | |||
PJ43169 | |||
PJ43172 | |||
PJ43172 | 5.1.0.0-P8CSS-IF012 - 4/27/2015 | ||
5.2.0.2-P8CSS-IF004 - 4/27/2015 | |||
5.2.1.0-P8CSS-IF002 - 4/27/2015 | |||
5.2.0.3-P8CPE-IF007 - 8/4/2015 | |||
5.2.1.2-P8CPE-IF001 - 8/4/2015 | |||
IBM Content Foundation (ICF) | 5.2.0 | ||
5.2.1 | PJ43169 | ||
PJ43169 | |||
PJ43172 | |||
PJ43172 | 5.2.0.2-P8CSS-IF004 - 4/27/2015 | ||
5.2.1.0-P8CSS-IF002 - 4/27/2015 | |||
5.2.0.3-P8CPE-IF007 - 8/4/2015 | |||
5.2.1.2-P8CPE-IF001 - 8/4/2015 | |||
FileNet Business Process Manager | 4.5.1 | ||
5.0.0 | |||
5.2.0 | PJ43170 | ||
PJ43171 | |||
PJ43174 | 4.5.1.4-P8PE-IF008 - 8/4/2015 | ||
5.0.0.8-P8PE-IF002 - 8/4/2015 | |||
eProcess-5.2.0-001.006 (Win, Sol, AIX, HP, HPUX only) - 8/4/2015 |
These releases are available on Fix Central: <http://www.ibm.com/support/fixcentral/>
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.
You should verify that applying the configuration changes recommended below does not cause any compatibility issues.
Mitigation is to disable RC4:
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 theProcess 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:
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 theProcess 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 theProcess 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:
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.