dbcve.org
Business Automation WorkflowApplication · Ibm

CVE-2019-4149

MEDIUM · 5.4 CVSS v3.1 Published 2019-09-05
Fix available
A fix is available. Upgrade to after 18.0.0.2 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 V18.0.0.0 through V18.0.0.2 and IBM Business Process Manager V8.6.0.0 through V8.6.0.0 Cumulative Fix 2018.03, V8.5.7.0 through V8.5.7.0 Cumulative Fix 2017.06, and V8.5.6.0 through V8.5.6.0 CF2 is vulnerable to cross-site scripting. This vulnerability allows users 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: 158415.

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 Business Automation Workflow and Business Process Manager contain a cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code that executes within a trusted user session, potentially leading to credential disclosure.

MitigationApply IBM cumulative fixes (CFs) or service packs that include the security patch for CVE-2019-4149. Refer to IBM Fix Central for version-specific patches.

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:>= 18.0.0.0, <= 18.0.0.2
Business Process ManagerApplication
Affected:= 8.5.6.0= 8.5.7.0= 8.6.0.0

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 the installed IBM product
    Determine whether the environment runs IBM Business Automation Workflow (BAW) or IBM Business Process Manager (BPM). Check the installation directory or product documentation to confirm the product name.
    Affected if The product is Business Automation Workflow or Business Process Manager.
  2. Check the installed version of Business Automation Workflow
    Locate the version information for BAW (typically found in installation directories, versioninfo files, or the WebSphere/Process Server administration console). Compare the version number to the affected range 18.0.0.0 through 18.0.0.2.
    Affected if The installed BAW version is 18.0.0.0, 18.0.0.1, or 18.0.0.2.
  3. Check the installed version of Business Process Manager
    Locate the version information for BPM (typically found in installation directories, versioninfo files, or the WebSphere/Process Server administration console). Compare the version number to the affected versions 8.5.6.0, 8.5.7.0, or 8.6.0.0.
    Affected if The installed BPM version is exactly 8.5.6.0, 8.5.7.0, or 8.6.0.0.
  4. Confirm the Web UI component is accessible
    Verify that the Web UI (Process Portal or similar web interface) is deployed and reachable. This may involve checking the application status in the WebSphere Administrative Console or confirming network accessibility of the web port.
    Affected if The Web UI is deployed and accessible to users.

A user is affected if they run Business Automation Workflow version 18.0.0.0-18.0.0.2 or Business Process Manager version 8.5.6.0, 8.5.7.0, or 8.6.0.0 with the Web UI component enabled 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.

From vendor data
Upgrade available Upgrade to a release after 18.0.0.2
Interim mitigation

Apply IBM cumulative fixes (CFs) or service packs that include the security patch for CVE-2019-4149. Refer to IBM Fix Central for version-specific patches.

Fix this in Business Automation Workflow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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