Cross-domain identity assumption via stale EJB principal
Published Jun 7, 2021 · Updated Aug 4, 2024
Privilege context switching error in WildFly before 20.0.0.Final allows remote authenticated users to assume another EJB caller's identity. EJBContext fails to restore the original principal after one EJB invokes another EJB assigned to a different security domain. Exploitation requires low-privileged access and a cross-domain EJB call, after which the retained principal grants unauthorized access to data and operations.
Summary
What happened
Privilege context switching error in WildFly before 20.0.0.Final allows remote authenticated users to assume another EJB caller's identity. EJBContext fails to restore the original principal after one EJB invokes another EJB assigned to a different security domain. Exploitation requires low-privileged access and a cross-domain EJB call, after which the retained principal grants unauthorized access to data and operations.
The record
- CVE
- CVE-2020-1719
- Published
- Jun 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- 389 Directory Server
- Product
- WildFly
- Classifications
- CWE-270
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=wildfly 20.0.0.Final
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