When using role-based authorization to configure EJB access, JACC permissions should be used to determine access. The implementation logic of the JACC workflow resulted in the authorization being incorrectly configured and wrongly delegated. As a result, the configured authorization modules (JACC, XACML, etc.) are never called and the JACC permissions are never used to determine access to an EJB. This flaw only affects JBoss Enterprise Application Platform 6. Earlier versions are not affected.
Acknowledgements: This issue was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team.
This issue has been addressed in following products: JBEAP 6 for RHEL 5 Via RHSA-2012:1591 https://rhn.redhat.com/errata/RHSA-2012-1591.html
This issue has been addressed in following products: JBEAP 6 for RHEL 6 Via RHSA-2012:1592 https://rhn.redhat.com/errata/RHSA-2012-1592.html
This issue has been addressed in following products: JBoss Enterprise Application Platform 6.0.1 Via RHSA-2012:1594 https://rhn.redhat.com/errata/RHSA-2012-1594.html
Statement: This issue did not affect JBoss Enterprise Application Platform versions 4.x and 5.x.