IBM Support

Security Bulletin: IBM Data Virtualization on Cloud Pak for Data is affected by critical vulnerability in Log4j (CVE-2021-44228)

Security Bulletin


Summary

There is a vulnerability in the version of the Log4j open source library that is part of IBM Data Virtualization on Cloud Pak for Data

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

Affected Product(s)DV Version(s)
CPD Version(s)
IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.3.02.5.0
IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.4.13.0.1
IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.5.03.5, 3.5 Refresh 1 - 9
IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.7.1 - 1.7.34.0 Refresh 1 - 3

Remediation/Fixes

Affected Product(s)DV Version(s)
CPD Version(s) Fixes
IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.3.02.5.0

Upgrade to version 1.5.0 patch version 1.5.0.0-270 (DV) /

3.5 Refresh 10 (CPD)

IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.4.13.0.1

Upgrade to version 1.5.0 patch version 1.5.0.0-270 (DV) /

3.5 Refresh 10 (CPD)

IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.5.0

3.5,

3.5 Refresh 1 - 9

Apply patch version 1.5.0.0-270 (DV) /

3.5 Refresh 10 (CPD)

IBM Data Virtualization(DV) on Cloud Pak for Data(CPD)1.7.1 - 1.7.34.0 Refresh 1 - 3

Update to version 1.7.3 (DV) /

4.0 Refresh 4 (CPD)

 

You must update the Cloud Pak for Data platform to version 4.0 Refresh 4 to install the Log4Shell fix for Data Virtualization.

To update Cloud Pak for Data platform to 4.0 Refresh 4, see the following links:

If you are upgrading from IBM Cloud Pak for Data 4.0 Refresh 3, the Data Virtualization pods will restart after the db2u operator is updated. If the db2u operator subscription installPlanApproval is set to "Automatic", the Data Virtualization pods will restart when the db2u operator catalog is updated. After the restart of the Data Virtualization pods is complete, you must also manually restart the header and worker pods to complete the Log4Shell fix. This manual restart can be performed by running the following command:

current_replicas=$(oc get sts c-db2u-dv-db2u -o jsonpath="{.spec.replicas}");oc scale sts c-db2u-dv-db2u --replicas=0; sleep 3m; oc scale sts c-db2u-dv-db2u --replicas=$current_replicas

If you are upgrading from a version of IBM Cloud Pak for Data other than 4.0 Refresh 3, you can restart Data Virtualization head and worker pods after the upgrade has finished successfully.

You can also run the following commands to delete old files from your updated Data Virtualization instance that contained old log4j binaries.

1. oc rsh c-db2u-dv-db2u-0
2. su - db2inst1
3. rm -rf /mnt/blumeta0/home/db2inst1/sqllib/datavirtualization/dvm_driver/log4j-api-2.8.2.jar /mnt/blumeta0/home/db2inst1/sqllib/datavirtualization/dvm_driver/log4j-core-2.8.2.jar /mnt/bludata0/dv/versioned/pre_migration/sqllib/datavirtualization/dvm_driver/log4j-api-2.8.2.jar /mnt/bludata0/dv/versioned/pre_migration/sqllib/datavirtualization/dvm_driver/log4j-core-2.8.2.jar
4. ${BIGSQL_CLI_DIR}/BIGSQL/package/scripts/bigsqlPexec.sh -w -c "rm -rf /mnt/blumeta0/home/db2inst1/sqllib/datavirtualization/dvm_driver/log4j-api-2.8.2.jar"
5. ${BIGSQL_CLI_DIR}/BIGSQL/package/scripts/bigsqlPexec.sh -w -c "rm -rf /mnt/blumeta0/home/db2inst1/sqllib/datavirtualization/dvm_driver/log4j-core-2.8.2.jar" 6. rm -rf /mnt/PV/versioned/uc_dsserver_shared/config/DATAVIRTUALIZATION_ENDPOINT_V1.7.3_20211119_164257.tar.gz /mnt/PV/versioned/uc_dsserver_shared/config/DATAVIRTUALIZATION_ENDPOINT_V1.7.3_20211119_164257.zip 7. cp /opt/ibm/qp_artifacts/archives/DATAVIRTUALIZATION_ENDPOINT_V1.7.3_20211119_164257.tar.gz /mnt/PV/versioned/uc_dsserver_shared/config 8. cp /opt/ibm/qp_artifacts/archives/DATAVIRTUALIZATION_ENDPOINT_V1.7.3_20211119_164257.zip /mnt/PV/versioned/uc_dsserver_shared/config

Additional Information

If you run a security vulnerability scanning tool on the Docker images, you might find that some of the affected packages at the affected version are still present on it. Those packages have been modified according to guidance provided by the log4j development team so that they are no longer vulnerable.

 

Workarounds and Mitigations

None

Get Notified about Future Security Bulletins

References

Off

Acknowledgement

Change History

22 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":"SSK1AQ","label":"IBM Data Virtualization"},"Component":"","Platform":[{"code":"PF043","label":"Red Hat"}],"Version":"1.3.0\/2.5.0, 1.4.1\/3.0.1, 1.5.0\/3.5, 1.5.0\/3.5 Refresh 1 - 9, 1.7.1 - 1.7.3\/4.0 Refresh 1 - 3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 January 2022

UID

ibm16536734