CVE-2020-17532 json
Apache ServiceComb Yaml remote deserialization vulnerability
published 5y ago modified 4mo ago also GHSA-px4w-rcv2-6x8x , EUVD-2022-1140
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- maven org.apache.servicecomb:java-chassis 1.3.2, 2.1.5
- apache java_chassis 2.1.5
Is CVE-2020-17532 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.38% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.servicecomb:java-chassis | >=1.0.0, <1.3.2 >=2.0.0, <2.1.5 |
1.3.2 2.1.5 |
Affected products
- Apache Software Foundation Apache ServiceComb-Java-Chassis
Classification
References
-
issues.apache.org
/jira/browse/SCB-2145
web, mailing-list, patch, vendor-advisory
-
github.com
/apache/servicecomb-java-chassis/commit/839a52e27c754cb5ce14f20063902f21065bd26c
web
-
github.com
/apache/servicecomb-java-chassis/commit/ba4fb37b6ab8bd3a6c3d0693f295d99a94879838
web
-
seclists.org
/oss-sec/2021/q1/60
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-17532
advisory
Sources
- CVE List CVE-2020-17532
- GitHub Advisory GHSA-px4w-rcv2-6x8x
- NVD CVE-2020-17532
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.