Security Bulletin: OpenSSH vulnerability affects IBM Db2® on Cloud Pak for Data, and Db2 Warehouse on Cloud Pak for Data

Summary

IBM has released the below fix for IBM Db2® on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data in response to the OpenSSH vulnerability found in multiple components. This bulletin identifies the steps to take to address the vulnerability.

Vulnerability Details

CVEID:CVE-2024-6387
**DESCRIPTION:**OpenSSH could allow a remote attacker to execute arbitrary code on the system, caused by a signal handler race condition. By sending a specially crafted request, an attacker could exploit this vulnerability to execute arbitrary code with root privileges on glibc-based Linux systems.
CVSS Base score: 8.1
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/296064 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)

Affected Products and Versions

Remediation/Fixes

IBM strongly recommends addressing the vulnerability now by applying the patch containing the fix for this issue. It can be applied to v5.0 to remediate this vulnerability.

This vulnerability was found in the following Db2U images in version 11.5.9.0-cn1 for Cloud Pak for Data.

1. db2u
2. db2u.restricted
3. db2u.db2wh (available on only amd64 platform)
4. db2u.qrep (available on only amd64 and ppc64le platform)

If you are on Db2 version 11.5.9.0-cn1 on IBM Cloud Pak for Data platform, a patch is required to replace these vulnerable images with the new ones containing the fix for CVE-2024-6387.

Patching instructions for the Db2 operator to apply the new images:

1. Add a new version of container images with a special build version tag on the cluster host by editing the db2u-release config map.
   e.g., oc edit cm db2u-release -n ${PROJECT_CPD_INST_OPERATORS}
   Copy the complete 11.5.9.0-cn1 images section into a new version called11.5.9.0-cn1-sb1.
2. Replace the affected images with the new images in the new 11.5.9.0-cn1-sb1section** **based on the platform you are on:
   1. amd64| “db2u”: “icr.io/db2u/db2u@sha256:9fa258d91947de8009da32612c647559885696206f4c14b80982edbd966e24e8”
   “db2u-restricted”: “icr.io/db2u/db2u.restricted@sha256:96bceb88f9edee2eca41f955139de8ffb4a08ae6a89f3d3b2803871781c2d164”
   “db2wh”: “icr.io/db2u/db2u.db2wh@sha256:5ce439471f39b9c65c25e557105f101c50bfd14612d0752dcdc3286045909360”
   “qrep”: “icr.io/db2u/db2u.qrep@sha256:335829ef1a954500007f5f0018b197571f4547f6a533db3eb22ca228a5455898”
   —|—
   ppc64le| “db2u”: “icr.io/db2u/db2u@sha256:2b8dc86f8e8e4637c30b007610774e691b092a7727753309536ad40b36e17b16”
   “db2u-restricted”: “icr.io/db2u/db2u.restricted@sha256:5b0f5874558a68cd92f31213c0bcd15ea7a2a86e29221f57f624884b80320872”
   “qrep”: “icr.io/db2u/db2u.qrep@sha256:c3e33d53d1a3edb8a9fc1cfccca693c7a6bb58d6eb3d568b96a0f19e3d6ed73a”
   s390x| “db2u”: “icr.io/db2u/db2u@sha256:a6ab29d93538439d1ac8a9f7ee6464e15ec0539eccdd3ce6860c44b329fa8499”
   “db2u-restricted”: “icr.io/db2u/db2u.restricted@sha256:c2f869d6ec3a5e22ccdd1dc4e12f45c12be849537de42b5aad84a23054e00819”
3. Save your changes to the db2u-release config map
4. Execute the oc patch command on each Db2uCluster custom resource:
   1. Run: oc patch db2ucluster <instance_id> --type merge -p ‘{“spec”:{“version”:“11.5.9.0-cn1-sb1”}}’
   2. Wait for the db2ucluster custom resource to become Ready
   3. Refresh the UI deployment details page to see the upgraded database patch version

Workarounds and Mitigations

None