Cross-user information access via shared RunAs identity
Published May 10, 2022 · Updated Aug 2, 2024
Incorrect authorization in WildFly 11 through 26.1.0 allows remote authenticated users to read other application users' information. EJBComponent stores the pre-switch SecurityIdentity in one shared incomingRunAsIdentity field, so overlapping RunAs calls make getCallerPrincipal() or isCallerInRole() use another call's identity. Exploitation requires Elytron, a RunAs-enabled EJB, and concurrent calls from multiple users; exposure is limited to application-scope data.
Summary
What happened
Incorrect authorization in WildFly 11 through 26.1.0 allows remote authenticated users to read other application users' information. EJBComponent stores the pre-switch SecurityIdentity in one shared incomingRunAsIdentity field, so overlapping RunAs calls make getCallerPrincipal() or isCallerInRole() use another call's identity. Exploitation requires Elytron, a RunAs-enabled EJB, and concurrent calls from multiple users; exposure is limited to application-scope data.
The record
- CVE
- CVE-2022-0866
- Published
- May 10, 2022
- Updated
- Aug 2, 2024
- Vendor
- 389 Directory Server
- Product
- WildFly
- Classifications
- CWE-368, CWE-863, CAPEC-26, CAPEC-29
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo