Authenticated code execution via Groovy report conditions
Published Jan 5, 2020 · Updated Aug 5, 2024
Code injection in Determine Contract Lifecycle Management 5.4 allows remote authenticated users to execute arbitrary code on the server. The report_edit.jsp report builder accepts attacker-controlled condition_Text as a Groovy scripted condition and executes it as Java without restricting shell-command access. Default roles, including the least-privileged Contract Viewer role, can run reports, so any application account can execute commands with the server process privileges.
Summary
What happened
Code injection in Determine Contract Lifecycle Management 5.4 allows remote authenticated users to execute arbitrary code on the server. The report_edit.jsp report builder accepts attacker-controlled condition_Text as a Groovy scripted condition and executes it as Java without restricting shell-command access. Default roles, including the least-privileged Contract Viewer role, can run reports, so any application account can execute commands with the server process privileges.
The record
- CVE
- CVE-2019-20155
- Published
- Jan 5, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- Determine SCLM report_edit.jsp Groovy code-execution requestfunctional · 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