Authenticated code execution via unchecked default expressions
Published Feb 12, 2020 · Updated Aug 4, 2024
Sandbox bypass in Jenkins Pipeline: Groovy Plugin 2.78 and earlier allows remote authenticated users to execute controller-JVM code. Default parameter expressions in CPS-transformed methods execute without the sandbox checks that should constrain untrusted Pipeline code. The user must be able to define and run a sandboxed Pipeline; successful exploitation executes arbitrary code with the controller process's privileges.
Summary
What happened
Sandbox bypass in Jenkins Pipeline: Groovy Plugin 2.78 and earlier allows remote authenticated users to execute controller-JVM code. Default parameter expressions in CPS-transformed methods execute without the sandbox checks that should constrain untrusted Pipeline code. The user must be able to define and run a sandboxed Pipeline; successful exploitation executes arbitrary code with the controller process's privileges.
The record
- CVE
- CVE-2020-2109
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy
- Classifications
- CWE-20, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 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 <=2.78
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.
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