CVE-2022-0866
mediumpriority · track · 21OT risk · elevatedEPSS 0.009 · 60 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (6)
Products and version ranges known to be affected.
- n/a wildfly≤ JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.enisa_euvdEU
- redhat jboss enterprise application platform≥ 7.1.0nvdUScpe:2.3:a:redhat:jboss_enterprise_application_platform:*:*:*:*:*:*:*:*
advisories (1)
Vendor and ecosystem advisories describing this.
- BIT-wildfly-2022-08662025-11-07vendor · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (16)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2022-0866cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2060929#c0cnnvd
- https://cxsecurity.com/cveshow/CVE-2022-0866/cnnvd
- https://packetstormsecurity.com/files/167423/Red-Hat-Security-Advisory-2022-4918-01.htmlcnnvd
- https://packetstormsecurity.com/files/168631/Red-Hat-Security-Advisory-2022-6782-01.htmlcnnvd
- https://packetstormsecurity.com/files/169727/Red-Hat-Security-Advisory-2022-7417-01.htmlcnnvd
- https://packetstormsecurity.com/files/169729/Red-Hat-Security-Advisory-2022-7410-01.htmlcnnvd
- https://vigilance.fr/vulnerability/Wildfly-user-access-via-Elytron-Security-38330cnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan