Authenticated code execution via arbitrary YAML types
Published Mar 25, 2020 · Updated Aug 4, 2024
Deserialization in Jenkins Pipeline: AWS Steps Plugin 1.40 and earlier allows remote authenticated users to execute code through YAML build input. The plugin's build steps pass attacker-controlled YAML to a parser that permits arbitrary type instantiation instead of restricting construction to safe types. Exploitation requires permission to supply a YAML input file to an affected build step and executes code in the Jenkins execution context.
Summary
What happened
Deserialization in Jenkins Pipeline: AWS Steps Plugin 1.40 and earlier allows remote authenticated users to execute code through YAML build input. The plugin's build steps pass attacker-controlled YAML to a parser that permits arbitrary type instantiation instead of restricting construction to safe types. Exploitation requires permission to supply a YAML input file to an affected build step and executes code in the Jenkins execution context.
The record
- CVE
- CVE-2020-2166
- Published
- Mar 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: AWS Steps
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 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.40
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.
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