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.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat JBoss Enterprise Application Platform |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1273046 is considered high due to unauthorized shutdown capabilities affecting JBoss EAP.
To fix REDHAT-BUG-1273046, ensure that only admin users are authorized to perform server shutdowns by applying the recommended patches from Red Hat.
REDHAT-BUG-1273046 affects all versions of JBoss EAP that do not have the necessary patches applied.
Any user with the roles Monitor, Deployer, or Auditor can exploit REDHAT-BUG-1273046 to shut down the EAP server.
The impact of REDHAT-BUG-1273046 can lead to service disruptions and loss of availability for applications running on the JBoss EAP server.