Security Bulletin: Apache Log4j Vulnerability Affects IBM Sterling File Gateway (CVE-2021-44228)

Summary

IBM Sterling File Gateway is impacted by Log4Shell (CVE-2021-44228), through the use of Apache Log4j’s JNDI logging feature. Final remediation images published below. As an alternative to the final remediation images, manual mitigation steps are also provided below.

Vulnerability Details

CVEID:CVE-2021-44228
**DESCRIPTION:**Apache Log4j could allow a remote attacker to execute arbitrary code on the system, caused by the failure to protect against attacker controlled LDAP and other JNDI related endpoints by JNDI features. By sending a specially crafted code string, an attacker could exploit this vulnerability to load arbitrary Java code on the server and take complete control of the system. Note: The vulnerability is also called Log4Shell or LogJam.
CVSS Base score: 10
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/214921 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)

Affected Products and Versions

Note that remote perimeter server, CLA2, OpsServer and external purge has been assessed for impact and were found to be not affected.

Due to concern surrounding Apache Log4j CVE-2021-44228 end-of-support stream IBM Sterling B2B Integrator Version 5.2.x has been assessed for impact the versions and fix packs below were found to be not affected by CVE-2021-44228:
5020605_3 and all lower fix packs
5020604 and all fix packs
5020603 and all fix packs
5020602 and all fix packs
5020601 and all fix packs
5020600 and all fix packs
5020500 and all fix packs
5020402 and all fix packs

Remediation/Fixes

IIM

Step 1: Apply IBM Sterling Filegateway IIM version 6.0.0.7, 6.0.3.5, 6.1.0.4, 6.1.1.0, 6.0.2.3 or 6.0.1.2

Step 2: Apply the remediating ifix 6.0.0.7_1, 6.0.3.5_1, 6.1.0.4_1 , 6.1.1.0_1, 6.0.2.3._1 or 6.0.1.2_1 that are located on Fix Central

Also for 6.1.1.0 after applying the remediating ifix 6.1.1.0_1, additionally follow the steps in this technote.

Docker & Containers

Step 1: Apply either IBM Sterling Filegateway Docker version 6.0.0.7, 6.0.3.5 or 6.1.0.4,

Step 2: Next apply one of the remediating ifixes below:

IBM Sterling Filegateway Docker version 6.0.0.7_1 on Fix Central

IBM Sterling Filegateway Docker version 6.0.3.5_1 on Fix Central

IBM Sterling Filegateway Container version 6.1.0.4_1

• Certified Container Image
• Helm Chart

Workarounds and Mitigations

If you are unable to apply the remediated fix packs above, as an alternative IBM Sterling File Gateway administrators should apply one of the following remediation steps below cased on deployment pattern.

The following instruction applies to B2Bi ASI node and Adapter Container node

1. Use dashboard UI to navigate to Operations -> System -> Performance -> Tuning -> Edit Performance Configuration
2. Add -Dlog4j2.formatMsgNoLookups=true to JVM Argument Suffix box in the page for Performance Tuning: JVM Parameters for Sever
3. If there is any adapter container node, do the same change to the page for Performance Tuning: JVM Parameters Container
4. Stop B2Bi
5. Run setupfiles.sh or setupfiles.cmd
6. Restart B2Bi

The following instruction applies to the Liberty server for B2Bi REST API

1. Edit <install_dir>\liberty\wlp\usr\servers\SIServer\jvm.options file and find the line that says -Dlog4j2.disable.jmx=true and open up a new line below that and add the following on a new line by itself: -Dlog4j2.formatMsgNoLookups=true
   Example:
   -Dlog4j2.disable.jmx=true
   -Dlog4j2.formatMsgNoLookups=true
2. Stop B2Bi
3. Restart B2Bi

The following instruction applies to B2Bi with Docker Container

1. Use dashboard UI to navigate to Operations -> System -> Performance -> Tuning -> Edit Performance Configuration
2. Add -Dlog4j2.formatMsgNoLookups=true to JVM Argument Suffix box in the page for Performance Tuning: JVM Parameters for Server
3. Liberty: update the setup.cfg LIBERTY_JVM_OPTIONS as LIBERTY_JVM_OPTIONS= -Dlog4j2.formatMsgNoLookups=true
4. Run docker run with run_all option for the new setup.cfg

The following instruction applies to B2Bi with OCP

1. Update values.yaml for B2Bi. Update the jvm option for the entries below in ibm-b2bi-case-bundle\charts\ibm-b2bi-prod\values.yaml

* libertyJvmOptions: -Dlog4j2.formatMsgNoLookups=true 
* asi: jvmOptions: -Dlog4j2.formatMsgNoLookups=true 
* ac: jvmOptions: -Dlog4j2.formatMsgNoLookups=true 
* api: jvmOptions: -Dlog4j2.formatMsgNoLookups=true 
* Update dataSetup: enabled: false 
* After saving values.yaml, run helm upgrade <helm_version>-f values.yaml . --recreate-pods
* Same steps need to be followed for ibm-sfg-case-bundle\charts\ibm-sfg-prod\values.yaml for SFG.

2. Restart B2Bi