CVE-2020-17532 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in org.apache.servicecomb:java-chassis. A fix is available for org.apache.servicecomb:java-chassis — see the affected versions and patch details below.
Arbitrary code execution in Apache ServiceComb java-chassis
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-17532 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.servicecomb:java-chassis☕org.apache.servicecomb:java-chassisReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
When handler-router component is enabled in servicecomb-java-chassis, authenticated user may inject some data and cause arbitrary code execution. The problem happens in versions between 2.0.0 ~ 2.1.3 and fixed in Apache ServiceComb-Java-Chassis 2.1.5
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.servicecomb:java-chassis | ≥ 1.0.0&&< 1.3.2 | 1.3.2org.apache.servicecomb:java-chassis:1.3.2 |
| ☕Maven | org.apache.servicecomb:java-chassis | ≥ 2.0.0&&< 2.1.5 | 2.1.5org.apache.servicecomb:java-chassis:2.1.5 |
Affected Products
java chassisapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.servicecomb:java-chassis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.servicecomb:java-chassis to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-17532 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2020-17532 in your dependencies?
Find it across Maven, including transitive dependencies.