This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is configured with a RunAs principal. In particular, the org.jboss.as.ejb3.component.EJBComponent class has an incomingRunAsIdentity field. This field is used by the org.jboss.as.ejb3.security.RunAsPrincipalInterceptor to keep track of the current identity prior to switching to a new identity created using the RunAs principal. The exploit consist that the EJBComponent#incomingRunAsIdentity field is currently just a SecurityIdentity. This means in a concurrent environment, where multiple users are repeatedly invoking an EJB that is configured with a RunAs principal, it's possible for the wrong the caller principal to be returned from EJBComponent#getCallerPrincipal. Similarly, it's also possible for EJBComponent#isCallerInRole to return the wrong value. Both of these methods rely on incomingRunAsIdentity. Affects all versions of JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=2060929#c0 | Issue Tracking Mitigation Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: redhat
Published: 2022-05-10T20:20:35
Updated: 2022-05-10T20:20:35
Reserved: 2022-03-04T00:00:00
Link: CVE-2022-0866
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-05-10T21:15:08.817
Modified: 2022-05-18T16:13:09.497
Link: CVE-2022-0866
JSON object: View
Redhat Information
No data.
CWE