CVE-2024-37528
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 · uneditedIBM Cloud Pak for Business Automation 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2, 23.0.1, and 23.0.2 is vulnerable to cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 294293.
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 · moderate confidenceStored cross-site scripting (XSS) vulnerability in IBM Cloud Pak for Business Automation Web UI allows privileged users to inject arbitrary JavaScript code that executes in other users' trusted sessions, potentially leading to credential disclosure.
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>= 18.0.0, <= 18.0.2>= 19.0.1, <= 19.0.3>= 20.0.1, <= 20.0.3= 21.0.1= 21.0.3= 22.0.1= 22.0.2= 23.0.1= 23.0.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Cloud Pak for Business Automation versionRun 'oc get icpa4ibm-cp4ba -n <namespace> -o jsonpath="{.spec.version}"' or check the operator CSV version via 'oc get csv -n <namespace>' and grep for ibm-cp4baAffected if The displayed version falls within 18.0.0-18.0.2, 19.0.1-19.0.3, 20.0.1-20.0.3, 21.0.1, 21.0.3, 22.0.1, 22.0.2, 23.0.1, or 23.0.2
-
Confirm Web UI component is deployed and accessibleCheck for the presence of the webui deployment pods: 'oc get pods -n <namespace> | grep -i webui' and verify the service is exposed: 'oc get svc -n <namespace> | grep -i webui'Affected if The Web UI pods are running and the service is exposed, making the vulnerable interface accessible to users
-
Verify privileged user access exists in the environmentCheck for users with admin or privileged roles who can access the Web UI: 'oc get users -n <namespace>' or review IBM Cloud Pak for Business Automation user role assignments via the administration consoleAffected if Privileged users (administrators, operators) exist and can log into the Web UI, enabling them to inject the malicious script
If the installed version matches any of the affected ranges (18.0.0-23.0.2) AND the Web UI is accessible to privileged users, the environment is vulnerable to stored XSS via CVE-2024-37528.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply IBM-provided patches for affected versions (18.0.0-23.0.2). Implement output encoding and input validation for user-supplied content in the Web UI as a defense-in-depth measure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37528 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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