First published: Mon Oct 19 2015(Updated: )
It was found that JBoss EAP did not properly authorize a user performing a shut down. An user with the role Monitor, Deployer, or Auditor could use this flaw to shut down the EAP server, which is an action restricted to admin users. The following commits introduced this issue: <a href="https://github.com/wildfly/wildfly-core/commit/6e5611b4c6">https://github.com/wildfly/wildfly-core/commit/6e5611b4c6</a> <a href="https://github.com/jbossas/jboss-eap/commit/a905e9a041">https://github.com/jbossas/jboss-eap/commit/a905e9a041</a> The context.getServiceRegistry call, which throws an exception when authorization fails, was replaced with a call to context.authorize, which only returns an authorization result.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Redhat Jboss Enterprise Application Platform | <=6.4.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.