Unauthenticated code execution via designer class loading
Published Sep 15, 2021 · Updated Aug 4, 2024
Incorrect authorization in UReport 2.2.9 allows remote attackers to execute arbitrary code through the web-based report designer. The unauthenticated designer invokes Java Class.forName on a pre-positioned malicious class, executing its static initializer when the JVM loads it. Network access to the designer page and prior placement of a malicious class on the server classpath are required, after which code runs in the application process.
Summary
What happened
Incorrect authorization in UReport 2.2.9 allows remote attackers to execute arbitrary code through the web-based report designer. The unauthenticated designer invokes Java Class.forName on a pre-positioned malicious class, executing its static initializer when the JVM loads it. Network access to the designer page and prior placement of a malicious class on the server classpath are required, after which code runs in the application process.
The record
- CVE
- CVE-2020-21124
- Published
- Sep 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Malicious Java class-loading proof of conceptproof of concept · demonstrated
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