{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.shardingsphere:shardingsphere. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1947 in the wild and no public exploit code.","fix":"Upgrade org.apache.shardingsphere:shardingsphere to 4.0.1 or later.","what":"CVE-2020-1947 is a critical unsafe deserialization vulnerability in Apache ShardingSphere(incubator), published on 11 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1947 and fix it if it is affected.\n\nWhat it is: CVE-2020-1947 is a critical unsafe deserialization vulnerability in Apache ShardingSphere(incubator), published on 11 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-1947 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.shardingsphere:shardingsphere (Maven): affected from 4.0.0-RC3; fixed in 4.0.1\n- org.apache.shardingsphere:shardingsphere (Maven): affected from 4.0.0-RC3; fixed in 4.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-1947/ (Markdown: https://insights.sbomify.com/CVE-2020-1947/index.md)","id":"CVE-2020-1947","markdown":"https://insights.sbomify.com/CVE-2020-1947/index.md","name":"CVE-2020-1947","record":{"aliases":["GHSA-v54f-xcmp-43cr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache ShardingSphere","requires_auth":"none","summary":"Attackers can achieve remote code execution by sending malicious YAML inputs to the ShardingSphere web console due to unsafe SnakeYAML deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"shardingsphere","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2020-03-11","github_poc":4,"max_poc_stars":31,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-03-11T03:15:25Z","kind":"github_poc","ref":"https://github.com/jas502n/CVE-2020-1947","stars":31,"title":"Apache ShardingSphere UI YAML解析远程代码执行漏洞"},{"date":"2020-03-11T12:35:56Z","kind":"github_poc","ref":"https://github.com/wsfengfan/CVE-2020-1947","stars":4,"title":"CVE-2020-1947 Python POC"},{"date":"2020-03-13T09:47:33Z","kind":"github_poc","ref":"https://github.com/shadowsock5/ShardingSphere_CVE-2020-1947","stars":1,"title":null},{"date":"2020-05-29T08:07:16Z","kind":"github_poc","ref":"https://github.com/StarkChristmas/CVE-2020-1947","stars":1,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Deserialization of Untrusted Data in Apache ShardingSphere","id":"CVE-2020-1947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Deserialization of Untrusted Data in Apache Dubbo","id":"CVE-2020-1948"},"packages":[{"ecosystem":"Maven","fixed":["4.0.1"],"introduced":["4.0.0-RC3"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere","purl":null,"source":"GHSA-v54f-xcmp-43cr"},{"ecosystem":"Maven","fixed":["4.0.1"],"introduced":["4.0.0-RC3"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere","purl":"pkg:maven/org.apache.shardingsphere/shardingsphere","source":"GHSA-v54f-xcmp-43cr"}],"prev":{"headline":"Apache SpamAssassin has an OS Command Injection vulnerability","id":"CVE-2020-1946"},"products":["Apache ShardingSphere(incubator)"],"published":"2020-03-11","related":[{"cvss_score":9.8,"headline":"Apache ShardingSphere-Proxy: MySQL authentication bypass","id":"CVE-2022-45347","kev_date_added":null,"published":"2022-12-22"},{"cvss_score":8.8,"headline":"ShardingSphere-Agent: Deserialization vulnerability in ShardingSphere Agent","id":"CVE-2023-28754","kev_date_added":null,"published":"2023-07-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apache Software Foundation"]},"summary":"Attackers can achieve remote code execution by sending malicious YAML inputs to the ShardingSphere web console due to unsafe SnakeYAML deserialization.","url":"https://insights.sbomify.com/CVE-2020-1947/"}