Authenticated code execution via unsafe YAML parsing
Published Mar 25, 2020 · Updated Aug 4, 2024
Remote code execution in Jenkins OpenShift Pipeline Plugin 1.0.56 and earlier allows remote authenticated users to run code via YAML files. The build step passes attacker-controlled YAML to a parser configured to instantiate arbitrary Java types rather than restricting construction to safe types. Control of a YAML input file consumed by the build step is required, and successful exploitation executes code in the Jenkins controller process.
Summary
What happened
Remote code execution in Jenkins OpenShift Pipeline Plugin 1.0.56 and earlier allows remote authenticated users to run code via YAML files. The build step passes attacker-controlled YAML to a parser configured to instantiate arbitrary Java types rather than restricting construction to safe types. Control of a YAML input file consumed by the build step is required, and successful exploitation executes code in the Jenkins controller process.
The record
- CVE
- CVE-2020-2167
- Published
- Mar 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- OpenShift Pipeline Plugin
- Classifications
- CWE-20, T1190
- 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.0.56
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