CVE-2020-1947 in the critical feed json
Deserialization of Untrusted Data in Apache ShardingSphere
published 6y ago modified 4mo ago also GHSA-v54f-xcmp-43cr , EUVD-2022-1188
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 33.9%
- EPSS 33.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
In Apache ShardingSphere(incubator) 4.0.0-RC3 and 4.0.0, the ShardingSphere's web console uses the SnakeYAML library for parsing YAML inputs to load datasource configuration. SnakeYAML allows to unmarshal data to a Java type By using the YAML tag. Unmarshalling untrusted data can lead to security flaws of RCE.
Patch / fix
- maven org.apache.shardingsphere:shardingsphere 4.0.1
Is CVE-2020-1947 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
33.92% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.shardingsphere:shardingsphere | >=4.0.0-RC3, <4.0.1 |
4.0.1 |
Affected products
- Apache Software Foundation Apache ShardingSphere(incubator)
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
Sources
- CVE List CVE-2020-1947
- GitHub Advisory GHSA-v54f-xcmp-43cr
- NVD CVE-2020-1947
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.