dbcve.org
Business Automation WorkflowApplication · Ibm

CVE-2024-54179

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to after 24.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Business Automation Workflow and IBM Business Automation Workflow Enterprise Service Bus 24.0.0, 24.0.1 and earlier unsupported versions are vulnerable to cross-site scripting. This vulnerability allows an authenticated user 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 · moderate confidence

Authenticated cross-site scripting (XSS) vulnerability in IBM Business Automation Workflow and IBM Business Automation Workflow Enterprise Service Bus Web UI. An authenticated attacker can inject arbitrary JavaScript code that may alter intended functionality and potentially disclose credentials within trusted sessions.

MitigationApply available vendor patches or upgrade to a supported version. Additionally, implement output encoding and input validation for user-supplied content in the Web UI to mitigate XSS attacks.

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
Business Automation WorkflowApplication
Affected:<= 24.0.1= 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
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 checks

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

  1. Identify installed IBM product
    Determine if IBM Business Automation Workflow (BAW) or IBM Business Automation Workflow Enterprise Service Bus (ESB) is installed in your environment. Check installed applications or running services for these product names.
    Affected if The product is IBM Business Automation Workflow or IBM Business Automation Workflow Enterprise Service Bus.
  2. Check BAW/ESB version
    Locate and inspect the installed version of IBM Business Automation Workflow or IBM Business Automation Workflow Enterprise Service Bus. Use the product's version lookup mechanism or check installation directories for version information.
    Affected if The installed version is 24.0.0, 24.0.1, or any version lower than or equal to 24.0.1.
  3. Verify Web UI is accessible
    Confirm that the Web UI component of IBM Business Automation Workflow or IBM Business Automation Workflow Enterprise Service Bus is deployed and accessible. Check if the web interface ports or endpoints are active.
    Affected if The Web UI is enabled and network-accessible, as the vulnerability exists specifically within this component.
  4. Confirm authentication is configured
    Verify that user authentication is enabled for the Web UI. Check the authentication configuration settings or security realm configuration for the application.
    Affected if Authentication is enabled for the Web UI, as this is an authenticated XSS vulnerability requiring a valid user session.

You are affected if you have IBM Business Automation Workflow or IBM Business Automation Workflow Enterprise Service Bus installed with version 24.0.0, 24.0.1, or any version up to and including 24.0.1, and the Web UI is accessible with authentication enabled.

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
Upgrade available Upgrade to a release after 24.0.1
Interim mitigation

Apply available vendor patches or upgrade to a supported version. Additionally, implement output encoding and input validation for user-supplied content in the Web UI to mitigate XSS attacks.

Recommended fix Moderate confidence

Version newer than 24.0.1 (refer to IBM security bulletin for exact fixed release)

  1. 1. Review IBM Business Automation Workflow security bulletins on www.ibm.com for the complete fix information
  2. 2. Identify the current installed version (24.0.0 or 24.0.1 or earlier)
  3. 3. Plan upgrade to a version newer than 24.0.1 as specified in IBM's security advisory
  4. 4. Back up all existing configurations and data
  5. 5. Test the upgrade in a non-production environment before deploying to production
  6. 6. Apply the upgrade following IBM's standard upgrade documentation
  7. 7. Verify the XSS vulnerability is resolved by testing that arbitrary JavaScript cannot be embedded in the Web UI
Caveat Review IBM upgrade documentation for potential configuration or compatibility changes between versions

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

Fix this in Business Automation Workflow Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54179 — 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-54179 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