Unauthorized EJB actions via ignored RunAs roles
Published Jan 23, 2020 · Updated Aug 6, 2024
Authorization bypass in affected Red Hat JBoss middleware releases allows remote attackers to execute EJB methods with unintended roles. EJBJACCPolicyModuleDelegate.checkWithPolicy derives current roles from the caller principal even when a run-as principal exists, ignoring roles declared with @RunAs. Reachability requires deployed EJB code that uses @RunAs; successful calls are authorized with caller roles rather than the component's declared run-as identity.
Summary
What happened
Authorization bypass in affected Red Hat JBoss middleware releases allows remote attackers to execute EJB methods with unintended roles. EJBJACCPolicyModuleDelegate.checkWithPolicy derives current roles from the caller principal even when a run-as principal exists, ignoring roles declared with @RunAs. Reachability requires deployed EJB code that uses @RunAs; successful calls are authorized with caller roles rather than the component's declared run-as identity.
The record
- CVE
- CVE-2012-5626
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- Red Hat
- Product
- Red Hat JBoss Portal
- Classifications
- T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=4
- Affected versionversion=5
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