Security Bulletin
Summary
A vulnerability in IBM Cloud Pak for Multicloud Management has been delivered in a HotFix for 2.3 FP9
Vulnerability Details
CVEID: CVE-2024-21534
DESCRIPTION: Jsonpath-plus could allow a remote attacker to execute arbitrary code on the system, caused by improper input sanitization and unsafe default usage of the vm module in Node.js. By exploiting the unsafe default usage of the vm module in Node.js, an attacker could exploit this vulnerability to inject and execute arbitrary code on the system.
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
CVSS Source: IBM X-Force
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 CP4MCM | 2.3 to 2.3 FP9 |
Remediation/Fixes
Steps to apply the hotfix:
1) Pull the images by running the below command:
docker pull docker://icr.io/cp/cp4mcm/itopsui@sha256:a3bea4406c0b76c4580044a4fcdc1ad827d67ee09f95004b6ad536b34695c8b0
docker pull docker://icr.io/cp/cp4mcm/agentbootstrap@sha256:1a6f937b50116e2858666fe903a719c8043a0c6bffa6220f6c81ed09934486bb
2) On CP4MCM, identify the Monitoring ClusterServiceVersion (CSV). The CSV name will be used in the next steps.
oc get csv -n management-monitoring | grep ibm-management-monitoring | awk '{print $1}'
3) Take a backup of the CSV file.
oc get csv -n management-monitoring <CSV-name> -o yaml >/tmp/csv-backup
4) Update the images on setup by executing the below command to edit the Monitoring ClusterServiceVersion (CSV) file :
oc edit csv -n management-monitoring <CSV-name>
5) Update the olm.relatedImage.<NAME> entries to use the new images. Change the following entries:
olm.relatedImage.itopsui: "icr.io/cp/cp4mcm/itopsui@sha256:a3bea4406c0b76c4580044a4fcdc1ad827d67ee09f95004b6ad536b34695c8b0"
olm.relatedImage.agentbootstrap: "icr.io/cp/cp4mcm/agentbootstrap@sha256:1a6f937b50116e2858666fe903a719c8043a0c6bffa6220f6c81ed09934486bb"
6) Save the changes and verify they have been applied.
Verification steps:
1) AMUI and agentbootstrap pods should get restarted once above changes are done
2) Verify if the images used by the recreated pod is correct
For itopsui (AMUI pod):
oc describe pod monitoring-amui-*
Search for the image ID of itopsui and it should match with the above sha value (a3bea4406c0b76c4580044a4fcdc1ad827d67ee09f95004b6ad536b34695c8b0)
For agentbootstrap (agentbootstrap pod):
oc describe pod monitoring-agentbootstrap-*
Search for the image ID of agentbootstrap and it should match with the above sha value (1a6f937b50116e2858666fe903a719c8043a0c6bffa6220f6c81ed09934486bb)
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
Change History
21 Feb 2025: 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:
21 February 2025
Initial Publish date:
21 February 2025
UID
ibm17183919