dbcve.org
Cloud Pak For Business AutomationApplication · Ibm

CVE-2024-41753

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Cloud Pak for Business Automation 24.0.0 through 24.0.0 IF004 and 24.0.1 through 24.0.1 IF001 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Cloud Pak for Business Automation versions 24.0.0 through 24.0.0 IF004 and 24.0.1 through 24.0.1 IF001 contains a reflected cross-site scripting vulnerability in the Web UI. An unauthenticated attacker can inject arbitrary JavaScript code that executes within a trusted user session, potentially leading to credential theft or session hijacking.

MitigationApply IBM's interim fixes IF004 for version 24.0.0 and IF001 for version 24.0.1. As a temporary compensating control, implement input validation and output encoding on web inputs, and consider deploying a Web Application Firewall.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud Pak For Business AutomationApplication
Affected:= 24.0.0= 24.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Cloud Pak for Business Automation version
    Use the OpenShift CLI (oc) to query the operator or product version: 'oc get ICP4ACluster -A -o jsonpath="{.items[0].status.version}"' or check the operator subscription: 'oc get subscription ibm-cloudpak-for-business-automation -n <namespace> -o jsonpath="{.status.currentCSV}"'. Alternatively, check the IBM Automation Platform incidents: 'oc get incidents -n <namespace>' or the deployed operand versions.
    Affected if The installed version is 24.0.0 or 24.0.1 without the respective interim fixes (IF004 for 24.0.0, IF001 for 24.0.1)
  2. Verify if Web UI component is deployed
    Check for the presence of Web UI pods or deployment configurations: 'oc get deployment -n <namespace> | grep -i webui' or 'oc get pods -n <namespace> | grep -i webui'. Also check the ICP4ACluster custom resource for Web UI configuration: 'oc get ICP4ACluster -n <namespace> -o jsonpath="{.items[0].spec.webui}"'.
    Affected if The Web UI component is deployed and accessible, as the XSS vulnerability exists in this specific component
  3. Confirm interim fix status
    Check the installed operator version or patch level. Query the CSV (ClusterServiceVersion) for the applied version: 'oc get csv -n <namespace> | grep ibm-cloudpak'. For 24.0.0, verify IF004 is applied by checking the operator version includes IF004. For 24.0.1, verify IF001 is applied. Look at the subscription channel or installed CSV name which typically contains the IF level.
    Affected if No interim fix (IF004 for version 24.0.0 or IF001 for version 24.0.1) has been applied to the installation
  4. Assess Web UI exposure
    Check if the Web UI service is exposed externally: 'oc get route -n <namespace> | grep -i webui' or review ingress configurations. Determine if the Web UI is reachable from untrusted networks, as the attacker needs to lure a user to click a crafted URL.
    Affected if The Web UI is externally accessible without additional authentication layers beyond the application login
  5. Review recent access logs for XSS patterns
    Examine HTTP access logs for the Web UI for suspicious patterns in URL parameters that may indicate exploitation attempts. Check for presence of '<script>', 'javascript:', or other HTML/JS injection patterns in request query strings. Use: 'oc logs -n <namespace> deployment/<webui-pod> --tail=1000 | grep -E "(<script|javascript:)"'
    Affected if Unusual XSS patterns appear in Web UI access logs, indicating potential exploitation attempts

A user is affected if IBM Cloud Pak for Business Automation version 24.0.0 (without IF004) or 24.0.1 (without IF001) is installed with the Web UI component deployed and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's interim fixes IF004 for version 24.0.0 and IF001 for version 24.0.1. As a temporary compensating control, implement input validation and output encoding on web inputs, and consider deploying a Web Application Firewall.

Recommended fix Moderate confidence

24.0.0 IF005 or later, 24.0.1 IF002 or later, or upgrade to 24.0.2+

  1. IBM Cloud Pak for Business Automation has released interim fixes for this vulnerability.
  2. For version 24.0.0, apply IBM Cloud Pak for Business Automation 24.0.0 IF005 or later.
  3. For version 24.0.1, apply IBM Cloud Pak for Business Automation 24.0.1 IF002 or later.
  4. Alternatively, upgrade to a later fixed release (24.0.2 or higher) when available.
  5. Consult IBM's official security bulletin for detailed patch installation instructions: https://www.ibm.com/support/pages/node/715929
Caveat Review IBM's migration documentation for any compatibility considerations when applying interim fixes or upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Business Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41753 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data