CVE-2016-5406 is an improper privilege-management vulnerability in Red Hat JBoss Enterprise Application Platform (EAP) 7 domain management. In affected releases, the domain controller can fail to propagate administrative role-based access control (RBAC) configuration to certain slave hosts. The resulting inconsistency in administrative authorization policy can allow an authenticated remote user to obtain privileges beyond those intended by the domain-wide RBAC configuration.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A domain-mode RBAC propagation flaw in JBoss EAP that may allow affected slave servers to gain elevated privileges.
Domain-controller RBAC propagation flaw that can permit privilege escalation on some slave servers.
EAP domain-controller RBAC propagation flaw that can allow privilege escalation on some slave systems.
Domain-controller RBAC configuration propagation flaw that can permit privilege escalation on certain slave systems.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.