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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published: 2022-05-10T20:20:35

Updated: 2024-08-02T23:40:04.505Z

Reserved: 2022-03-04T00:00:00

Link: CVE-2022-0866

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2022-05-10T21:15:08.817

Modified: 2024-11-21T06:39:33.650

Link: CVE-2022-0866

cve-icon Redhat

Severity : Moderate

Publid Date: 2022-05-03T00:00:00Z

Links: CVE-2022-0866 - Bugzilla