Authenticated code execution via unfiltered EJB deserialization
Published Jun 22, 2020 · Updated Aug 4, 2024
Unsafe deserialization in WildFly Application Server before 20.0.0.Final allows remote authenticated users to execute code through EJB. WildFly accepts serialized objects received by applications through remote JNDI or EJB features without applying validation or deserialization filters. Reachability requires an application using the affected JNDI or EJB features and access accepted by the configured remoting security realm; successful exploitation compromises the server process.
Summary
What happened
Unsafe deserialization in WildFly Application Server before 20.0.0.Final allows remote authenticated users to execute code through EJB. WildFly accepts serialized objects received by applications through remote JNDI or EJB features without applying validation or deserialization filters. Reachability requires an application using the affected JNDI or EJB features and access accepted by the configured remoting security realm; successful exploitation compromises the server process.
The record
- CVE
- CVE-2020-10740
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- WildFly
- Product
- WildFly Application Server
- Classifications
- CWE-502, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2020CVE 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=Versions before 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