CVE-2022-0866
published 2022-05-10CVE-2022-0866: 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…
PriorityP428medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
0.84%
53.8th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| redhat | jboss_enterprise_application_platform | >= 7.1.0 | — |
| redhat | openstack_platform | — | — |
| redhat | wildfly | — | — |
| redhat | wildfly | — | — |
| redhat | wildfly | >= 11.0.0 < 26.1.1 | 26.1.1 |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
wildfly: Wildfly management of EJB Session context returns wrong caller principal with Elytron Security enabled
vendor_redhat·2022-05-03·CVSS 5.3
CVE-2022-0866 [MEDIUM] CWE-863 wildfly: Wildfly management of EJB Session context returns wrong caller principal with Elytron Security enabled
wildfly: Wildfly management of EJB Session context returns wrong caller principal with Elytron Security enabled
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 Run
GHSA
GHSA-pjxg-p9c7-7c3v: 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
ghsa_unreviewed·2022-05-11
CVE-2022-0866 [MEDIUM] CWE-863 GHSA-pjxg-p9c7-7c3v: 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
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#getCallerPrincipa
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2022-05-10
Published