Authenticated code execution via unsafe YAML deserialization
Published Jan 25, 2021 · Updated Feb 13, 2025
Unsafe deserialization in Apache ServiceComb Java Chassis 2.0.0 through 2.1.3 allows remote authenticated users to execute code. RouterRuleCache passes routing-rule YAML to SnakeYAML's general-purpose constructor, allowing attacker-selected type tags to instantiate arbitrary classes. The handler-router component must be enabled and authenticated access is required; successful exploitation runs code in the affected service process.
Summary
What happened
Unsafe deserialization in Apache ServiceComb Java Chassis 2.0.0 through 2.1.3 allows remote authenticated users to execute code. RouterRuleCache passes routing-rule YAML to SnakeYAML's general-purpose constructor, allowing attacker-selected type tags to instantiate arbitrary classes. The handler-router component must be enabled and authenticated access is required; successful exploitation runs code in the affected service process.
The record
- CVE
- CVE-2020-17532
- Published
- Jan 25, 2021
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache ServiceComb Java Chassis
- Classifications
- CWE-502, CWE-20, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 2021CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=Apache ServiceComb-Java-Chassis 2.x 2.0.0 to 2.1.3
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