Security Bulletin
Summary
IBM Concert uses React which is vulnerable to remote code execution.
Vulnerability Details
CVEID: CVE-2025-55182
DESCRIPTION: A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.
CWE: CWE-502: Deserialization of Untrusted Data
CVSS Source: cve-assign@fb.com
CVSS Base score: 10
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| IBM Concert Software | 2.1 |
Remediation/Fixes
IBM strongly recommends addressing the vulnerability now.
| Product(s) | Version(s) | Remediation/Fix/Instructions |
| IBM Concert Software | 2.1 | Download and follow installation instructions below for IBM Concert Software 2.1.0 patch03 from IBM Entitled Registry (ICR) |
Instructions for installing 2.1.0 patch03 on OCP
- Access to the cluster where IBM Concert 2.1.0 is installed along with dataapps
- POC customers should reach out to IBM for registry and keys for the concert images.
Download the patch image
If your target cluster is behind an air gapped firewall with no access to the internet to pull images, not even with white-listing or proxying, you will need to replicate the images to your data center.
You can use skopeo copy or docker pull/tag/push to replicate images to your private registry if your cluster has no access to the IBM Container registry on the internet.
Apply the patch
1. Identify the namespace where dataapps is installed on the cluster
2. Edit the dataapps-end-product-backend deployment on the namespace
kubectl -n <dataapps-ns> edit deployment dataapps-end-product-backend
spec.template.spec.image tocp.icr.io/cp/concert/dataapps-end-product-backend:v2.1.0.patch03-410-20251212.022508-v2.1.0-patches
kubectl -n <dataapps-ns> get pods
dataapps-end-product-backend-* pods are healthyIntroduction
This document outlines the instructions to install IBM Data Apps v2.1.0.0 patch03
Before you begin
Ensure you have the following
- Access to the machine where IBM Concert v2.1.0.0 is installed
- POC customers should reach out to IBM for registry and keys for the concert images.
Download the patch image
If your target VM is behind an air gapped firewall with no access to the internet to pull images, not even with white-listing or proxying, you will need to replicate the images to your data center.
#!/bin/bash -e
export REGISTRY="na.artifactory.swg-devops.com/hyc-roja-platform-engineering-team-docker-local/concert"
export REG_USER="<will be provided by IBM>"
export REG_KEY="<will be provided by IBM>"
export DATAAPPS_IMAGE_NAME="dataapps-end-product-backend"
export DATAAPPS_IMAGE_GA_TAG="v2.1.0-394-20251017.153859-v2.1.0.x"
export DATAAPPS_IMAGE_PATCHED_TAG="v2.1.0.patch03-410-20251212.022508-v2.1.0-patches"
export DATAAPPS_REGISTRY="cp.icr.io/cp/concert"
export DOCKER_EXE="podman"
$DOCKER_EXE login ${REGISTRY} --username=${REG_USER} --password=${REG_KEY}
$DOCKER_EXE pull ${REGISTRY}/${DATAAPPS_IMAGE_NAME}:${DATAAPPS_IMAGE_PATCHED_TAG}
Applying the patch
Stop Data Apps
ibm-concert/ibm-dataapps-std/bin/stop
Retag image
$DOCKER_EXE tag ${REGISTRY}/${DATAAPPS_IMAGE_NAME}:${DATAAPPS_IMAGE_PATCHED_TAG} ${DATAAPPS_REGISTRY}/${DATAAPPS_IMAGE_NAME}:${DATAAPPS_IMAGE_PATCHED_TAG}
Update container.conf file with the patched image tag. I.e. ibm-dataapps-end-product-backend
cat ibm-concert/ibm-dataapps-std/etc/ibm-dataapps-end-product-backend.conf
docker_image_name=dataapps-end-product-backend
container_name=ibm-dataapps-end-product-backend # This is only used to stop and remove containers from a previous installation (1.1.0)
legacy_container_name=dataapps-end-product-backend
patch_image_tag=v2.1.0.patch03-410-20251212.022508-v2.1.0-patches
Start the ibm-dataapps-end-product-backend container by running the following command
ibm-concert/ibm-dataapps-std/bin/start
Validate the patch
$DOCKER_EXE container ls should show the patched image tag for the container
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
Change History
15 Dec 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:
15 December 2025
Initial Publish date:
15 December 2025
UID
ibm17254812