Security Bulletin: A security vulnerability has been identified in Apache Log4j (CVE-2021-44228) in IBM Maximo Asset Configuration Manager and IBM Maximo for Aviation.

Security Bulletin

Summary

Apache log4j 2 library is used by Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation). This bulletin provides a remediation for the Apache log4j 2 vulnerability (CVE-2021-44228)

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

Component	Apache Log4J 2 Version Used
IBM Maximo Asset Configuration Manager 7.6.7.3 / IBM Maximo for Aviation 7.6.8.2	2.12.1 - Java 8
IBM Maximo Asset Configuration Manager 7.6.7.2 / IBM Maximo for Aviation 7.6.8.1	2.12.1 - Java 8
IBM Maximo Asset Configuration Manager 7.6.7.1 / IBM Maximo for Aviation 7.6.8.0	2.8 - Java 8
IBM Maximo Asset Configuration Manager 7.6.7.0 / IBM Maximo for Aviation 7.6.7.1	2.8 - Java 8
IBM Maximo Asset Configuration Manager 7.6.6.0 / IBM Maximo for Aviation 7.6.6.0	2.8 - Java 7

Remediation/Fixes

IBM strongly recommends addressing the vulnerability by executing the manual patching steps depending on the Component.

Component	Action
IBM Maximo Asset Configuration Manager 7.6.7.3	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17" guidance below.
IBM Maximo for Aviation 7.6.8.2	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17" guidance below.
IBM Maximo Asset Configuration Manager 7.6.7.2	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17" guidance below.
IBM Maximo for Aviation 7.6.8.1	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17" guidance below.
IBM Maximo Asset Configuration Manager 7.6.7.1	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17 (Java 8)" guidance below.
IBM Maximo for Aviation 7.6.8.0	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17 (Java 8)" guidance below.
IBM Maximo Asset Configuration Manager 7.6.7.0	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17 (Java 8)" guidance below.
IBM Maximo for Aviation 7.6.7.1	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17 (Java 8)" guidance below.
IBM Maximo Asset Configuration Manager 7.6.6.0	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.12.3 (Java 7)" guidance below.
IBM Maximo for Aviation 7.6.6.0	Follow the "How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.12.3 (Java 7)" guidance below.

How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.17 (Java 8)

This a manual process to download the Apache log4j 2.17 from Apache and address the vulnerability.

1) Stop the Maximo application servers and BDI services.

2) Delete the existing log4j2 jar files (log4j-api-2.x.jar and log4j-core.2.jar) from the following locations:

a) <maximo_home>/applications/maximo/lib
b) <bdi_home>/lib (by default this is <maximo_home>/tools/maximo/v8/lib but quite often customers will run multiple instances of the BDI on separate servers).

3) Replace the deleted log4j2 jars with the 2.17 versions (log4j-api-2.17.0.jar and log4j-core.2.17.0.jar -https://www.apache.org/dyn/closer.lua/logging/log4j/2.17.0/apache-log4j-2.17.0-bin.zip)

4) Rebuild/redeploy the maximo.ear file using the normal process.

5) Edit and update any BDI script files which the customer uses to launch the BDI service so the "classpath" java command line argument references the 2.17.0 versions of the log4j2 jar files.
By default these scripts are located in: <bdi_home>/cmd

6) On Windows machines where the BDI is running as a Windows service the following additional steps should be performed:
a) Stop the BDI (v8) windows services.
b) Delete the existing windows service using the script located at: "<bdi_home>/cmd/delete (run as administrator).bat"
c) Edit the file: "bdi_home>/cmd/install (run as administrator).bat" and modify the "--classpath" attribute to use the new version of the log4j2 files.
d) Execute the file "bdi_home>/cmd/install (run as administrator).bat" to reinstall the BDI Windows service.
e) Restart the BDI Windows Service.

How to manually get Build Data Interpreter (BDI) in IBM Maximo Asset Configuration Manager (ACM) and IBM Maximo for Aviation (Aviation) updated to Apache log4j 2.12.3 (Java 7)

This a manual process to download the Apache log4j 2.12.3 from Apache and address the vulnerability.

https://www.apache.org/dyn/closer.lua/logging/log4j/2.12.3/apache-log4j-2.12.3-bin.zip

a) <maximo_home>/applications/maximo/lib (log4j-1.2-api-2.12.3.jar and log4j-core.2.12.3.jar)
b) <bdi_home>/lib (log4j-api-2.12.3.jar and log4j-core.2.12.3.jar)

4) Rebuild/redeploy the maximo.ear file using the normal process.

5) Edit and update any BDI script files which the customer uses to launch the BDI service so the "classpath" java command line argument references the 2.12.3 versions (log4j-api-2.12.3.jar and log4j-core.2.12.3.jar) of the log4j2 jar files.
By default these scripts are located in: <bdi_home>/cmd

6) On Windows machines where the BDI is running as a Windows service the following additional steps should be performed:
a) Stop the BDI (v8) windows services.
b) Delete the existing windows service using the script located at: "<bdi_home>/cmd/delete (run as administrator).bat"
c) Edit the file: "bdi_home>/cmd/install (run as administrator).bat" and modify the "--classpath" attribute to use the new version of the log4j2 files.
d) Execute the file "bdi_home>/cmd/install (run as administrator).bat" to reinstall the BDI Windows service.
e) Restart the BDI Windows Service.

Workarounds and Mitigations

N/A

Get Notified about Future Security Bulletins

Subscribe to My Notifications to be notified of important product support alerts like this.

References

Complete CVSS v3 Guide
On-line Calculator v3

Off

Acknowledgement

Change History

13 Dec 2021: Initial Publication

*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

Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.

Document Location

Worldwide

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKSJ","label":"Maximo Asset Configuration Manager"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.7.1, 7.6.7, 7.6.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS5RRF","label":"IBM Maximo for Aviation"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.8, 7.6.7, 7.6.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Tips

Security Bulletin: A security vulnerability has been identified in Apache Log4j (CVE-2021-44228) in IBM Maximo Asset Configuration Manager and IBM Maximo for Aviation.