Fix Readme
Abstract
A new vulnerability with log4j has been detected. MAS Monitor uses log4j in all releases and interim fixes are now available for our 8.4, 8.5 and 8.6 releases. More details of the vulnerability are available here: https://nvd.nist.gov/vuln/detail/CVE-2021-44228.
This is also fixed in an interim fix on top of our official 8.6.1 fix pack. It will be rolled into the official 8.6.2 fix pack.
Content
To receive the interim fix update your Red Hat OpenShift deployments for each of the Monitor API pods to point to the newly published fix image in IBM Cloud Registry.
Steps:
First, disable the Monitor operator by decrementing the number of pods instantiated by the operator deployment from 1 to 0.
Now go each of these 5 deployments: rest-meta, rest-kpi, rest-master, rest-datalake and rest-dscmanager.
Change the image tag from the released version to this image version
For 8.6.1 the interim fix version is:
8.6.10
For example:
Update
image: 'cp.icr.io/cp/monitor/rest-meta:8.6.8'
to
image: 'cp.icr.io/cp/monitor/rest-meta:8.6.10'
For 8.5:
8.5.7-pre.8.5.hotfix
For 8.4:
8.4.12-pre.8.4.hotfix
After the pods restart the interim fix has been applied
Move to this directory on each pod.
cd /opt/was/liberty/wlp/usr/servers/default/dropins
List the files in the war.
unzip -l *.war
Verify your log4j.jar is version 2.17.1 in 8.6.1 and 2.15 in previous versions.Reenable your operator to automatically install/receive future fixpacks as they are released on OLM.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeKAAU","label":"Maximo Application Suite->MAS Applications->Monitor"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
12 January 2022
UID
ibm16526168