Jboss Enterprise Application PlatformApplication · Redhat
CVE-2016-5406
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 · uneditedThe domain controller in Red Hat JBoss Enterprise Application Platform (EAP) 7.x before 7.0.2 allows remote authenticated users to gain privileges by leveraging failure to propagate administrative RBAC configuration to all slaves.
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 confidenceThe domain controller in Red Hat JBoss EAP 7.x before 7.0.2 fails to propagate Role-Based Access Control (RBAC) administrative configurations to subordinate slave domain controllers. This allows remote authenticated users to potentially gain elevated privileges by accessing functionality that should be restricted under RBAC policies but is accessible due to incomplete configuration synchronization.
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 Enterprise Application PlatformApplication
<= 7.0.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the installed JBoss EAP versionCheck your JBoss EAP installation to confirm the exact version number. In a domain deployment, this can be verified through the management console or by querying the domain controller's version information.Affected if The installed version is 7.0.1 or earlier (versions up to and including 7.0.1 are affected, 7.0.2 and later are not)
-
Confirm domain mode is in useDetermine whether the JBoss EAP instance is running in domain mode with a master domain controller and one or more slave domain controllers. This vulnerability only applies to domain mode deployments.Affected if The environment is running in domain mode with a domain controller hierarchy
-
Identify subordinate slave domain controllersCheck the domain configuration to enumerate all registered slave domain controllers that sync configuration from the master domain controller.Affected if There are one or more slave domain controllers configured in the domain
-
Inspect RBAC configuration on master and slavesCompare the Role-Based Access Control (RBAC) configuration settings between the master domain controller and each slave domain controller to identify any inconsistencies or missing policy propagations.Affected if RBAC policies configured on the master are not present or differ on slave domain controllers
A user is affected if they are running JBoss EAP version 7.0.1 or earlier in domain mode with slave controllers where RBAC settings configured on the master are not synchronized to the slaves.
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 dataUpgrade to JBoss EAP 7.0.2 or later to ensure RBAC configuration is properly propagated to all domain controller slaves. Alternatively, manually audit and enforce consistent RBAC settings across all domain nodes.
Fix this in Jboss Enterprise Application Platform
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5406 — 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-5406 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