Controller code execution via unintercepted constructors
Published Mar 9, 2020 · Updated Aug 4, 2024
Sandbox bypass in Jenkins Script Security Plugin 1.70 and earlier allows remote authenticated users to execute code in the controller JVM. Constructor handling permits crafted super-constructor calls and bodies to execute without interception by the Groovy sandbox. The attacker must have permission to specify and run sandboxed scripts, after which arbitrary controller-context code execution is available.
Summary
What happened
Sandbox bypass in Jenkins Script Security Plugin 1.70 and earlier allows remote authenticated users to execute code in the controller JVM. Constructor handling permits crafted super-constructor calls and bodies to execute without interception by the Groovy sandbox. The attacker must have permission to specify and run sandboxed scripts, after which arbitrary controller-context code execution is available.
The record
- CVE
- CVE-2020-2134
- Published
- Mar 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Script Security Plugin
- Classifications
- CWE-863, T1211
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 9, 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=unspecified <=1.70
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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