Jboss Bpm SuiteApplication · Redhat
CVE-2017-2674
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 · uneditedJBoss BRMS 6 and BPM Suite 6 before 6.4.3 are vulnerable to a stored XSS via several lists in Business Central. The flaw is due to lack of sanitation of user input when creating new lists. Remote, authenticated attackers that have privileges to create lists can store scripts in them, which are not properly sanitized before showing to other users, including admins.
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 confidenceJBoss BRMS 6 and BPM Suite 6 before 6.4.3 contain a stored XSS vulnerability in Business Central. Authenticated users with privileges to create lists can inject malicious scripts through user input that is not properly sanitized before being displayed to other users, including administrators.
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
>= 6.0.0, < 6.4.3CVSS 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.0/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 JBoss BRMS/BPM Suite installationLocate the JBoss installation directory and check for BRMS or BPM Suite components. Look for business-central war files or check the application server's deployed applications.Affected if JBoss BRMS or BPM Suite 6 is installed and running
-
Determine the installed versionCheck the version of JBoss BRMS/BPM Suite. This is typically found in the product's manifest, version file, or in the administration console. Common locations include the product's documentation directory or the deployed business-central web application.Affected if The installed version is >= 6.0.0 and < 6.4.3
-
Verify Business Central is accessibleConfirm that the Business Central web interface is deployed and accessible. Access the Business Central URL (typically at /business-central) and verify you can log in with an authenticated account.Affected if Business Central is deployed and accessible via web interface
-
Check for list creation privilegesReview user permissions in Business Central administration. Determine if the current user or any user account has privileges to create or edit lists within Business Central.Affected if Authenticated users have privileges to create or modify lists in Business Central
Your environment is affected if JBoss BRMS or BPM Suite 6.0.0 through 6.4.2 is installed with Business Central accessible to users who have list creation privileges.
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 data6.4.3
Upgrade to JBoss BRMS/BPM Suite 6.4.3 or later which contains the fix. Additionally, implement proper input validation and output encoding for all user-supplied data in Business Central list creation functionality.
Fix this in Jboss Bpm Suite
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2674 — 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-2017-2674 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