Jboss Bpm SuiteApplication · Redhat
CVE-2016-6344
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 · uneditedRed Hat JBoss BPM Suite 6.3.x does not include the HTTPOnly flag in a Set-Cookie header for session cookies, which makes it easier for remote attackers to obtain potentially sensitive information via script access to the cookies.
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 confidenceRed Hat JBoss BPM Suite 6.3.x fails to set the HTTPOnly flag on session cookies in Set-Cookie headers. Without this flag, session cookies are accessible via JavaScript (document.cookie), enabling malicious scripts in cross-site scripting (XSS) attacks to steal session identifiers and impersonate users.
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.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 BPM Suite versionCheck the installed version of Red Hat JBoss BPM Suite by inspecting the product installation directory or startup logs. Look for version files or examine the manifest in the jboss-modules.jar or related jars.Affected if The installed version is exactly 6.3.x (the specific affected version)
-
Locate the web.xml deployment descriptorFind the web.xml file in the deployed web application under the WEB-INF directory. This is typically in the deployments folder under the WAR file structure.Affected if The web.xml file exists and contains a session-config element without the http-only-cookie element or with http-only-cookie set to false.
-
Verify session-config settings in web.xmlOpen the web.xml file and locate the <session-config> element. Check whether the <http-only-cookie> sub-element is present and set to true. If absent or set to false, HTTPOnly is not enabled.Affected if The <session-config> section either lacks <http-only-cookie> entirely or has it explicitly set to false.
-
Test actual session cookie headersAuthenticate to the JBoss BPM Suite application and inspect the Set-Cookie response headers using browser developer tools or a tool like curl. Look for the JSESSIONID cookie in the response headers.Affected if The Set-Cookie header for JSESSIONID does not include the HttpOnly attribute.
A user is affected if they are running JBoss BPM Suite version 6.3 and their session cookies lack the HttpOnly flag in either the web.xml configuration or actual Set-Cookie response headers.
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 dataConfigure the application server to include the HttpOnly attribute on all session cookies. For JBoss EAP/WildFly, this is typically configured in the web.xml deployment descriptor or via the session-config element.
Fix this in Jboss Bpm Suite
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6344 — 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-2016-6344 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