dbcve.org
Jboss Bpm SuiteApplication · Redhat

CVE-2016-5401

HIGH · 8.8 CVSS v3.0 Published 2017-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-site request forgery (CSRF) vulnerability in Red Hat JBoss BRMS and BPMS 6 allows remote attackers to hijack the authentication of users for requests that modify instances via a crafted web page.

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

Cross-site request forgery (CSRF) vulnerability in Red Hat JBoss BRMS and BPMS 6 allows remote attackers to hijack the authentication of users for requests that modify instances via a crafted web page. Attackers can trick authenticated users into unknowingly submitting malicious requests that modify business process instances or rule data.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing endpoints and validate these tokens server-side for every POST/PUT/DELETE request. Additionally, configure same-site cookie attributes and implement referer/origin header validation as defense-in-depth.

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
Jboss Bpm SuiteApplication
Affected:= 6.0.0
Jboss Enterprise Brms PlatformApplication
Affected:= 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 JBoss BRMS/BPMS version
    Check the installed version of Red Hat JBoss Enterprise BRMS Platform or JBoss BPM Suite. This is typically found in the product's about panel, version file, or by querying the running application server's management console for the installed packages.
    Affected if The installed version is exactly 6.0.0 for either Red Hat JBoss BPM Suite or Red Hat JBoss Enterprise BRMS Platform.
  2. Verify CSRF token protection on state-changing endpoints
    Inspect the web application's form submissions and AJAX requests that perform POST, PUT, or DELETE operations on business process instances or rule data. Examine whether each state-changing request includes a synchronizer token (anti-CSRF token) in the request parameters or headers.
    Affected if State-changing endpoints lack anti-CSRF tokens in their requests, allowing attackers to forge requests on behalf of authenticated users.
  3. Inspect server-side token validation logic
    Examine the server-side code or configuration that handles state-changing requests. Verify that the application validates the presence and correctness of anti-CSRF tokens for every POST, PUT, and DELETE request to business process or rule modification endpoints.
    Affected if Server-side validation of CSRF tokens is missing or not enforced on endpoints that modify process instances or rule data.
  4. Check cookie configuration for same-site attribute
    Review the application's session cookie configuration or the underlying application server (JBoss) settings to determine if the session cookies have the SameSite attribute configured.
    Affected if Session cookies lack the SameSite attribute, providing no defense-in-depth protection against CSRF attacks.

The environment is affected if running JBoss BRMS or BPMS version 6.0.0 AND the application lacks anti-CSRF token validation on state-changing endpoints that modify business process instances or rule data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing endpoints and validate these tokens server-side for every POST/PUT/DELETE request. Additionally, configure same-site cookie attributes and implement referer/origin header validation as defense-in-depth.

Fix this in Jboss Bpm Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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