Unauthenticated code execution via Groovy scripts
Published Apr 6, 2021 · Updated Aug 4, 2024
Code injection in OpenIAM before 4.2.0.3 allows remote attackers to execute arbitrary code by submitting a Groovy script. Public disclosures identify the Groovy script facility as the execution path but do not name the endpoint, function, or validation failure that accepts the script. No authentication or user interaction is required, and successful exploitation compromises the server's confidentiality, integrity, and availability.
Summary
What happened
Code injection in OpenIAM before 4.2.0.3 allows remote attackers to execute arbitrary code by submitting a Groovy script. Public disclosures identify the Groovy script facility as the execution path but do not name the endpoint, function, or validation failure that accepts the script. No authentication or user interaction is required, and successful exploitation compromises the server's confidentiality, integrity, and availability.
The record
- CVE
- CVE-2020-13420
- Published
- Apr 6, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 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.
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