wildfly: Wildfly management of EJB Session context returns wrong caller principal with Elytron Security enabled
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | Wildfly | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7 | |||
| wildfly | cpe:/a:redhat:jboss_enterprise_application_platform:7.4 | RHSA-2022:4922 | 2022-06-06T00:00:00Z |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | |||
| eap7-wildfly-0:7.4.5-3.GA_redhat_00001.1.el8eap | cpe:/a:redhat:jboss_enterprise_application_platform:7.4::el8 | RHSA-2022:4919 | 2022-06-06T00:00:00Z |
| Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | |||
| eap7-wildfly-0:7.4.5-3.GA_redhat_00001.1.el7eap | cpe:/a:redhat:jboss_enterprise_application_platform:7.4::el7 | RHSA-2022:4918 | 2022-06-06T00:00:00Z |
| Red Hat Single Sign-On 7 | |||
| wildfly | cpe:/a:redhat:red_hat_single_sign_on:7 | RHSA-2022:6787 | 2022-10-04T00:00:00Z |
| Red Hat Single Sign-On 7.5 for RHEL 7 | |||
| rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el7sso | cpe:/a:redhat:red_hat_single_sign_on:7.5::el7 | RHSA-2022:6782 | 2022-10-04T00:00:00Z |
| Red Hat Single Sign-On 7.5 for RHEL 8 | |||
| rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el8sso | cpe:/a:redhat:red_hat_single_sign_on:7.5::el8 | RHSA-2022:6783 | 2022-10-04T00:00:00Z |
| Red Hat Single Sign-On 7.6.1 | |||
| wildfly | cpe:/a:redhat:red_hat_single_sign_on:7.6.1 | RHSA-2022:7417 | 2022-11-03T00:00:00Z |
| Red Hat Single Sign-On 7.6 for RHEL 7 | |||
| rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el7sso | cpe:/a:redhat:red_hat_single_sign_on:7.6::el7 | RHSA-2022:7409 | 2022-11-03T00:00:00Z |
| Red Hat Single Sign-On 7.6 for RHEL 8 | |||
| rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el8sso | cpe:/a:redhat:red_hat_single_sign_on:7.6::el8 | RHSA-2022:7410 | 2022-11-03T00:00:00Z |
| Red Hat Single Sign-On 7.6 for RHEL 9 | |||
| rh-sso7-0:1-5.el9sso | cpe:/a:redhat:red_hat_single_sign_on:7.6::el9 | RHSA-2022:7411 | 2022-11-03T00:00:00Z |
| rh-sso7-javapackages-tools-0:6.0.0-7.el9sso | cpe:/a:redhat:red_hat_single_sign_on:7.6::el9 | RHSA-2022:7411 | 2022-11-03T00:00:00Z |
| rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el9sso | cpe:/a:redhat:red_hat_single_sign_on:7.6::el9 | RHSA-2022:7411 | 2022-11-03T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-15908 | 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. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.902% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:redhat:wildfly:27.0.0:alpha1:*:*:*:*:*:* |