Remote code execution via unrestricted YAML constructors
Published Apr 16, 2020 · Updated Aug 4, 2024
Deserialization in Jenkins Yaml Axis Plugin 0.2.0 and earlier allows remote authenticated users to execute code via crafted YAML. YamlFileLoader and YamlTextLoader pass file or inline YAML to SnakeYAML's unrestricted default constructor, enabling arbitrary type instantiation. Exploitation requires Matrix-job configuration access or control of the SCM repository used by an existing job, and successful execution compromises the Jenkins controller.
Summary
What happened
Deserialization in Jenkins Yaml Axis Plugin 0.2.0 and earlier allows remote authenticated users to execute code via crafted YAML. YamlFileLoader and YamlTextLoader pass file or inline YAML to SnakeYAML's unrestricted default constructor, enabling arbitrary type instantiation. Exploitation requires Matrix-job configuration access or control of the SCM repository used by an existing job, and successful execution compromises the Jenkins controller.
The record
- CVE
- CVE-2020-2179
- Published
- Apr 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Yaml Axis Plugin
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 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.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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