Authenticated sandbox bypass via AST annotations
Published Feb 12, 2020 · Updated Aug 4, 2024
Improper input validation in Jenkins Script Security Plugin 1.69 and earlier allows remote authenticated users to execute arbitrary code via crafted Groovy annotations. During script compilation, AST-transforming annotations applied to imports or nested inside other annotations evade the plugin's sandbox restrictions. Exploitation requires Overall/Read permission and reaches code execution on the Jenkins controller JVM, with confidentiality, integrity, and availability impact.
Summary
What happened
Improper input validation in Jenkins Script Security Plugin 1.69 and earlier allows remote authenticated users to execute arbitrary code via crafted Groovy annotations. During script compilation, AST-transforming annotations applied to imports or nested inside other annotations evade the plugin's sandbox restrictions. Exploitation requires Overall/Read permission and reaches code execution on the Jenkins controller JVM, with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2020-2110
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Script Security Plugin
- 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 <=1.69
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