Security Bulletin: Vulnerability in Apache Log4j affects Cloud Pak for Security (CVE-2021-44228)

Summary

Cloud Pak for Security (CP4S) v1.9.0.0 and earlier is impacted by Log4Shell (CVE-2021-44228), through the use of Apache Log4j’s JNDI logging feature. This vulnerability has been addressed in the updated versions of CP4S images. Please see remediation steps below to apply fix. All customers are encouraged to act quickly to update their systems. Please note, this security bulletin has been superseded by Security Bulletin: Cloud Pak for Security is vulnerable to denial of service and arbitrary code execution due to Apache Log4j (CVE-2021-45105 and CVE-2021-45046) - see https://www.ibm.com/support/pages/node/6541156.

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

Remediation/Fixes

For Cloud Pak for Security 1.8.x and 1.9.x :

Ensure that you are logged in to the cluster by using either of the following oc login commands:

Using username and password:

oc login <openshift_url> -u <username> -p <password>

Using a token:

oc login --token=<token> --server=<openshift_url>

Check the current value of imagePullPolicy using the command :

oc get -n <CP4S_NAMESPACE> cp4sthreatmanagement threatmgmt -o yaml | grep imagePullPolicy:

If imagePullPolicy is not set to “Always” :

oc patch -n <CP4S_NAMESPACE> cp4sthreatmanagement threatmgmt --type merge --patch ‘{“spec”:{“extendedDeploymentConfiguration”:{“imagePullPolicy”:“Always”}}}’

Else, if the imagePullPolicy value is already set to “Always” :

oc delete pod -lsequence=idrmapp -n <CP4S_NAMESPACE>

After executing either of the above commands the pods will restart which can be monitored using :

oc get pods -n <CP4S_NAMESPACE> -w**

**

For Cloud Pak for Security 1.7.2.0 :

Ensure that you are logged in to the cluster by using either of the following oc login commands:

Using username and password:

oc login <openshift_url> -u <username> -p <password>

Using a token:

oc login --token=<token> --server=<openshift_url>

Select your CP4S namespace :

oc project <CP4S_NAMESPACE>

Check the current value of imagePullPolicy :

oc get iscinventory iscplatform -o yaml | grep imagePullPolicy:

If the value of imagePullPolicy is not set to “Always” :

oc patch iscinventory iscplatform --type merge --patch ‘{“spec”:{“definitions”:{“imagePullPolicy”: “Always”}}}’ && oc delete pod -lname=sequences

Else if the value of the imagePullPolicy is already set to “Always” :

o_c delete pod -lsequence=idrmapp_

After executing either of the above commands the idrm pods will restart which can be monitored using :

oc get pods -w

Workarounds and Mitigations

None