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: https://github.com/wildfly/wildfly-core/commit/6e5611b4c6 https://github.com/jbossas/jboss-eap/commit/a905e9a041 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.
Acknowledgements: This issue was discovered by Ladislav Thon of Red Hat Middleware Quality Engineering.
This issue has been addressed in the following products: JBoss Enterprise Application Platform Via RHSA-2015:2541 https://rhn.redhat.com/errata/RHSA-2015-2541.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 6 Via RHSA-2015:2539 https://rhn.redhat.com/errata/RHSA-2015-2539.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 5 Via RHSA-2015:2538 https://rhn.redhat.com/errata/RHSA-2015-2538.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 7 Via RHSA-2015:2540 https://rhn.redhat.com/errata/RHSA-2015-2540.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 6 Via RHSA-2015:2542 https://rhn.redhat.com/errata/RHSA-2015-2542.html