Security Bulletin
Summary
Multiple vulnerabilities found in IBM Data Privacy Risk Assessment for Cloud Pak for Data
Vulnerability Details
CVEID: CVE-2025-27363
DESCRIPTION: An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
CWE: CWE-787: Out-of-bounds Write
CVSS Source: NVD
CVSS Base score: 8.1
CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
CVEID: CVE-2024-47176
DESCRIPTION: CUPS is a standards-based, open-source printing system, and `cups-browsed` contains network printing functionality including, but not limited to, auto-discovering print services and shared printers. `cups-browsed` binds to `INADDR_ANY:631`, causing it to trust any packet from any source, and can cause the `Get-Printer-Attributes` IPP request to an attacker controlled URL. When combined with other vulnerabilities, such as CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177, an attacker can execute arbitrary commands remotely on the target machine without authentication when a malicious printer is printed to.
CWE: CWE-1327: Binding to an Unrestricted IP Address
CVSS Source: IBM X-Force
CVSS Base score: 7.5
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
CVEID: CVE-2024-47076
DESCRIPTION: CUPS is a standards-based, open-source printing system, and `libcupsfilters` contains the code of the filters of the former `cups-filters` package as library functions to be used for the data format conversion tasks needed in Printer Applications. The `cfGetPrinterAttributes5` function in `libcupsfilters` does not sanitize IPP attributes returned from an IPP server. When these IPP attributes are used, for instance, to generate a PPD file, this can lead to attacker controlled data to be provided to the rest of the CUPS system.
CWE: CWE-20: Improper Input Validation
CVSS Source: NVD
CVSS Base score: 8.6
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N)
CVEID: CVE-2024-47177
DESCRIPTION: Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-47076, CVE-2024-47175, CVE-2024-47176. Reason: This candidate is a duplicate of CVE-2024-47076, CVE-2024-47175, and CVE-2024-47176. Notes: All CVE users should reference CVE-2024-47076, CVE-2024-47175, and/or CVE-2024-47176 instead of this candidate. This CVE was issued to a vulnerability that is dependent on CVE-2024-47076, CVE-2024-47175, and CVE-2024-47176. According to rule 4.2.15 of the CVE CNA rules, \"CNAs MUST NOT assign a different CVE ID to a Vulnerability that is fully interdependent with another Vulnerability. The Vulnerabilities are effectively the same single Vulnerability and MUST use one CVE ID.
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
CVSS Source: IBM X-Force
CVSS Base score: 6.1
CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L)
CVEID: CVE-2024-47175
DESCRIPTION: CUPS is a standards-based, open-source printing system, and `libppd` can be used for legacy PPD file support. The `libppd` function `ppdCreatePPDFromIPP2` does not sanitize IPP attributes when creating the PPD buffer. When used in combination with other functions such as `cfGetPrinterAttributes5`, can result in user controlled input and ultimately code execution via Foomatic. This vulnerability can be part of an exploit chain leading to remote code execution (RCE), as described in CVE-2024-47176.
CWE: CWE-20: Improper Input Validation
CVSS Source: NVD
CVSS Base score: 9.8
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| IBM Data Privacy Risk Assessment for Cloud Pak for Data | 4.5.2, 4.5.3, 4.6, 4.6.1, 4.6.2, 4.6.3, 4.6.4, 4.6.5, 4.7.1, 4.7.2, 4.7.3, 4.8, 4.8.1, 4.8.3, 5.0, 5.2,5.3 |
Remediation/Fixes
IBM strongly recommends addressing the vulnerability now by upgrading.
| Affected Product(s) | Fixed Version(s) |
| IBM Data Privacy Risk Assessment for Cloud Pak for Data | 5.3.0 |
DPRA 5.3.0 CVE Hotfix - Installation Instructions
Summary description
This patch updates the image of the DPRA operator pod (ibm-cpd-dpra-operator) to v1.20.500. All other images are left unchanged.
The operator is installed through OLM, so the image is changed in the operator ClusterServiceVersion (CSV). Editing the Deployment directly does not work, because OLM reverts the change.
How to apply instructions
Before you begin, make sure that you have the oc CLI installed and are logged in to the cluster with permission to edit ClusterServiceVersions in the operator namespace.
Step 1 and the substeps cover downloading and copying images to a local private registry for an air-gapped environment.
Step 2 and the substeps cover applying the patch using the online IBM entitled registry, or using the images downloaded to the local private registry from Step 1.
-
To apply the patch in an air-gapped environment, proceed with the following steps.
- Log in to the OpenShift console as the cluster admin.
-
Prepare the authentication credentials to access the IBM production repository. Use the same auth.json file used for CASE download and image mirroring. An example directory path:
${HOME}/.airgap/auth.jsonOr create an auth.json file that contains credentials to access icr.io and your local private registry. For example:
{ "auths": { "icr.io": {"email":"unused","auth":"<base64 encoded id:apikey>"}, "<private registry hostname>": {"email":"unused","auth":"<base64 encoded id:password>"} } }For more information about the auth.json file, see containers-auth.json - syntax for the registry authentication file.
-
Install skopeo by running:
yum install skopeo -
To confirm the path for the local private registry to copy the hotfix images to, run the following command:
oc describe pod <hotfix image pod> | grep -i "image:"<hotfix image pod> is the pod name of the DPRA operator.
-
To get the local private registry source details, run the following commands:
oc get imageContentSourcePolicy oc describe imageContentSourcePolicy [cloud-pak-for-data-mirror]The local private registry mirror repository and path details should be in the output of the describe command:
mirrors: ${PRIVATE_REGISTRY_LOCATION}/cpopen/ source: icr.io/cpopenFor more information about mirroring of images, see Configuring your cluster to pull Cloud Pak for Data images.
-
Use the skopeo command to copy the patch images from the IBM production registry to the local private registry:
NOTE: When copy/pasting the "skopeo" command below, it is recommended to copy the command into a text editor to ensure there are no additional newline characters. Remove any additional newline characters. Then copy/paste the command from the text editor to the command line. If these steps are not done, the command may fail.
DPRA operator
skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://icr.io/cpopen/ibm-cpd-dpra-operator@sha256:fe085c850c4bec6a517d73237e5643a94faa84b5a688aa2d432a2b6de11a635d \ docker://<local registry>/cpopen/ibm-cpd-dpra-operator@sha256:fe085c850c4bec6a517d73237e5643a94faa84b5a688aa2d432a2b6de11a635dskopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://icr.io/cpopen/ibm-cpd-dpra-operator-bundle@sha256:ff23a20a5d4a73f04a570f202cc2bd7bf4b00f18f42debd03a95b7c74d543fde \ docker://<local registry>/cpopen/ibm-cpd-dpra-operator-bundle@sha256:ff23a20a5d4a73f04a570f202cc2bd7bf4b00f18f42debd03a95b7c74d543fdeskopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://icr.io/cpopen/ibm-cpd-dpra-operator-catalog@sha256:92d2011f35937ff4c04a63eb0ccff096199818a6703a9cb8cd7dbadc8c8cb827 \ docker://<local registry>/cpopen/ibm-cpd-dpra-operator-catalog@sha256:92d2011f35937ff4c04a63eb0ccff096199818a6703a9cb8cd7dbadc8c8cb827DPRA operand images
skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/calibrate-ic-cp4d@sha256:0f44204c636764be54c1fba9eb0b105f8f4e51ffb7107e1005a7c5b549dfa39b \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/calibrate-ic-cp4d@sha256:0f44204c636764be54c1fba9eb0b105f8f4e51ffb7107e1005a7c5b549dfa39bskopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/calibrate-jsu-cp4d@sha256:3f644f5fef6d723ba880c0eb824e5379b9fc31de24318aa6e02a548a31e1cbfb \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/calibrate-jsu-cp4d@sha256:3f644f5fef6d723ba880c0eb824e5379b9fc31de24318aa6e02a548a31e1cbfbskopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/calibrate_ui_frontend@sha256:d58ca89073b8f36a67c49acc54ddee12ab663f4c9c0836bbb675e807000a5f06 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/calibrate_ui_frontend@sha256:d58ca89073b8f36a67c49acc54ddee12ab663f4c9c0836bbb675e807000a5f06skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/calibrate_ui_backend@sha256:dbee866ad88e5e91a81ae455fcb6a42f8f121c8e751931c80a8f0e0c5bcd3421 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/calibrate_ui_backend@sha256:dbee866ad88e5e91a81ae455fcb6a42f8f121c8e751931c80a8f0e0c5bcd3421skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/cp4d-calibrate-percona-server-mongodb@sha256:4f4f7400159ea44368ec02c0e1ddbd99f2321a2a0f50e3427be5d95a4400b3aa \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/cp4d-calibrate-percona-server-mongodb@sha256:4f4f7400159ea44368ec02c0e1ddbd99f2321a2a0f50e3427be5d95a4400b3aaskopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/cp4d-calibrate-sbe-fingerprint@sha256:8d333efe9fdb8441b5824b0f7720ade79474d2aec7fd1b36fee647537040e77a \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/cp4d-calibrate-sbe-fingerprint@sha256:8d333efe9fdb8441b5824b0f7720ade79474d2aec7fd1b36fee647537040e77askopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/calibrate-k8s-util-cli@sha256:bcdd878e2bf87f094e359f139440848d6cd39dce37818292e76088b15806a493 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/calibrate-k8s-util-cli@sha256:bcdd878e2bf87f094e359f139440848d6cd39dce37818292e76088b15806a493skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/cp4d-hashicorp-vault@sha256:b63a102f71a7918cf821f042532b46cdb11846cab1f325f95ab6400ce30a9158 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/cp4d-hashicorp-vault@sha256:b63a102f71a7918cf821f042532b46cdb11846cab1f325f95ab6400ce30a9158skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/cp4d-integration@sha256:3a9ee4b6a8d035f40f5116e1f8ec5fd710e574057010d8a62ef915886993f236 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/cp4d-integration@sha256:3a9ee4b6a8d035f40f5116e1f8ec5fd710e574057010d8a62ef915886993f236skopeo copy --all --authfile "<folder path>/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/cpd/ibm-cpd-calibrate/cp4d-db2-drivers@sha256:fa175c5d317ef66554b19a2c210bcc43d1d99ac744aef5310bee80e3318b4980 \ docker://<local registry>/cp/cpd/ibm-cpd-calibrate/cp4d-db2-drivers@sha256:fa175c5d317ef66554b19a2c210bcc43d1d99ac744aef5310bee80e3318b4980
-
To install the patch using the online IBM entitled registry, or using the images downloaded from Step 1, proceed with the following commands.
Replace ${OPERATOR_NAMESPACE} with the project namespace where the DPRA operator is installed (cpd-operators, for example):
export OPERATOR_NAMESPACE=<enter your operator namespace>Set the operator image to the hotfix image, pinned by digest:
export OPERATOR_IMAGE="icr.io/cpopen/ibm-cpd-dpra-operator@sha256:fe085c850c4bec6a517d73237e5643a94faa84b5a688aa2d432a2b6de11a635d"If you copied the image to a local private registry in Step 1, or your cluster uses a mirror registry, replace icr.io/cpopen in the OPERATOR_IMAGE value with your registry path. Keep the same digest.
NOTE: When copy/pasting each "oc patch" command below, please ensure that it is contained on a single line without line breaks. Also, if any spaces are introduced by the copy/paste, they must be removed. If these steps are not done, the command may fail.
DPRA operator
-
Find the DPRA operator CSV:
export CSV=$(oc get csv -n ${OPERATOR_NAMESPACE} -o name | grep -i dpra-operator | head -1) echo ${CSV}The command should print one CSV name. If it prints nothing, the DPRA operator is not installed in this namespace.
-
Find the operator container in the CSV:
oc get ${CSV} -n ${OPERATOR_NAMESPACE} -o jsonpath='{range .spec.install.spec.deployments[*]}{.name}{"\n"}{end}' oc get ${CSV} -n ${OPERATOR_NAMESPACE} -o jsonpath='{range .spec.install.spec.deployments[0].spec.template.spec.containers[*]}{.name}{"\t"}{.image}{"\n"}{end}'Check that the container named ibm-cpd-dpra-operator is in the list and note its index. The patch in step 4 uses index 0 for both the deployment and the container. If your output differs, change those numbers in the patch.
-
Save a backup of the DPRA operator CSV currently deployed on the cluster:
oc get ${CSV} -n ${OPERATOR_NAMESPACE} -o yaml > dpra_csv_backup_<date>.yamlwhere <date> is the date you are applying the patch.
-
Run the following command to patch the operator image in the CSV:
oc patch ${CSV} -n ${OPERATOR_NAMESPACE} --type=json -p '[{"op":"replace","path":"/spec/install/spec/deployments/0/spec/template/spec/containers/0/image","value":"'"$OPERATOR_IMAGE"'"}]' -
Verify the patch. Run the following commands:
oc get pods -n ${OPERATOR_NAMESPACE} -w | grep dpraWait for the DPRA operator pod to restart, then press Ctrl+C to stop watching.
oc get pods -n ${OPERATOR_NAMESPACE} -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}' | grep dpraThe output should show the hotfix image digest.
oc get ${CSV} -n ${OPERATOR_NAMESPACE}After a period of time, the PHASE of the CSV should be Succeeded.
-
How to revert instructions
Put the original operator image back with the same patch, using the image value from the backup file saved in step 3 of "How to apply instructions".
DPRA operator
-
Run the following command to restore the original operator image in the CSV. Replace <original image from backup> with the image of the ibm-cpd-dpra-operator container in the dpra_csv_backup_<date>.yaml file:
oc patch ${CSV} -n ${OPERATOR_NAMESPACE} --type=json -p '[{"op":"replace","path":"/spec/install/spec/deployments/0/spec/template/spec/containers/0/image","value":"<original image from backup>"}]' -
Wait for the DPRA operator pod to restart. Run the following commands to confirm that the original image is running and the CSV is healthy:
oc get pods -n ${OPERATOR_NAMESPACE} -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}' | grep dpra oc get ${CSV} -n ${OPERATOR_NAMESPACE}After a period of time, the PHASE of the CSV should be Succeeded.
Known Issues
Operator image patch is replaced by a newer CSV
Issue: This patch changes the image in the installed CSV only. If the Subscription later installs a newer CSV, the newer CSV replaces this patch and the operator runs the image defined in the newer CSV.
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
Change History
16 Nov 2026: 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
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
18 November 2026
Initial Publish date:
16 November 2026
UID
ibm17296710