Authenticated code execution via unsafe YAML deserialization
Published Feb 12, 2020 · Updated Aug 4, 2024
Unsafe YAML deserialization in Jenkins Google Kubernetes Engine Plugin 0.8.0 and earlier allows remote authenticated users to execute code. The plugin's build step passes attacker-controlled YAML input 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 the build step and results in code execution on the Jenkins controller.
Summary
What happened
Unsafe YAML deserialization in Jenkins Google Kubernetes Engine Plugin 0.8.0 and earlier allows remote authenticated users to execute code. The plugin's build step passes attacker-controlled YAML input 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 the build step and results in code execution on the Jenkins controller.
The record
- CVE
- CVE-2020-2121
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Google Kubernetes Engine Plugin
- Classifications
- Unavailable
- 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 <=0.8.0
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
No sourced classifications are available.
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