Code execution via unsafe YAML class instantiation
Published Mar 13, 2020 · Updated Aug 4, 2024
Uncontrolled class instantiation in Apache Commons Configuration 2.2 through 2.6 allows attackers to execute code through crafted YAML files. YAMLConfiguration.read creates SnakeYAML parsers with permissive constructors and passes input to Yaml.load, allowing explicit type tags to instantiate Java classes. An application must load an untrusted YAML file, and resulting code executes within the host application's process and privilege context.
Summary
What happened
Uncontrolled class instantiation in Apache Commons Configuration 2.2 through 2.6 allows attackers to execute code through crafted YAML files. YAMLConfiguration.read creates SnakeYAML parsers with permissive constructors and passes input to Yaml.load, allowing explicit type tags to instantiate Java classes. An application must load an untrusted YAML file, and resulting code executes within the host application's process and privilege context.
The record
- CVE
- CVE-2020-1953
- Published
- Mar 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Commons Configuration
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 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=2.2
- Affected versionversion=2.3
- Affected versionversion=2.4
- Affected versionversion=2.5
- Affected versionversion=2.6
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