Security Bulletin: A security vulnerability has been identified in Apache log4j versions 2.0 beta 9 - 2.14 (CVE-2021-44228) in IBM Maximo Scheduler Optimization

Summary

Apache log4j 2 library is used by IBM Maximo Scheduler Optimization (MSO). This bulletin provides remediation for the Apache log4j 2 vulnerability (CVE-2021-44228) by performing the applicable steps to the MSO product.

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

2.13.2

IBM Maximo Scheduler Optimization | Application| Platform Independent| 8.0.0|

2.13.2

Remediation/Fixes

How to manually get Maximo Scheduler Optimization 7.6.8 (MSO) updated to Apache log4j 2.17.1

This manual process updates the Log4j 2 reference inside of the build.gradle file.

1. Modify the following build.gradle files:

<mso_home>/maintenance-optimization-framework/mof-execution-service/build.gradle
<mso_home>/maintenance-optimization-framework/mof-rest-service/build.gradle
<mso_home>/maintenance-optimization-framework/mof-common/build.gradle

and replace the lines:

//Logging - Log4j2
implementation group: ‘org.apache.logging.log4j’, name: ‘log4j-api’, version: ‘2.13.2’
implementation group: ‘org.apache.logging.log4j’, name: ‘log4j-core’, version: ‘2.13.2’

With:

//Logging - Log4j2
implementation group: ‘org.apache.logging.log4j’, name: ‘log4j-api’, version: ‘2.17.1’
implementation group: ‘org.apache.logging.log4j’, name: ‘log4j-core’, version: ‘2.17.1’

2. Execute the build script buildMOF.sh (Linux) or buildMOF.bat (Windows) to rebuild the application archive files.

3. Rebuild the MSO application Docker images and redeploy them to the container registry that is used to host the images.

4. Terminate any currently active MSO API (rest service) or execution service pods so that new pods, using the updated images, are created.

How to manually get Maximo Scheduler Optimization 8.0.0 (MSO) updated to Apache log4j 2.17.1

Update the Maximo Scheduler Optimization 8.0.0 installed on Maximo Application Suite (MAS) to Version 8.0.3 of MSO.

Update Maximo Scheduler Optimization application

When new versions of applications are available, you can update the deployed applications.

To update an application:

1. From the Suite Administration Applications pane, select the Addon tab and find the Maximo Scheduler Optimization application that you want to update.
2. On the application summary page confirm the 8.0.3 or > version, click Update

Workarounds and Mitigations

For MSO 7.6.8 version Update the current Log4j 2.13.2 library with =>2.17.1 reference inside the build.gradle file.

For MSO 8 version just update to the latest version available after 8.0.3