{"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-2023-28754 in the wild and no public exploit code.","fix":"Upgrade org.apache.shardingsphere:shardingsphere to 5.4.0 or later.","what":"CVE-2023-28754 is a high-severity unsafe deserialization vulnerability in Apache Software Foundation ShardingSphere-Agent, published on 19 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28754 and fix it if it is affected.\n\nWhat it is: CVE-2023-28754 is a high-severity unsafe deserialization vulnerability in Apache Software Foundation ShardingSphere-Agent, published on 19 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-28754 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.shardingsphere:shardingsphere (Maven): affected all versions; fixed in 5.4.0\n- org.apache.shardingsphere:shardingsphere (Maven): affected all versions; fixed in 5.4.0\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-2023-28754/ (Markdown: https://insights.sbomify.com/CVE-2023-28754/index.md)","id":"CVE-2023-28754","markdown":"https://insights.sbomify.com/CVE-2023-28754/index.md","name":"CVE-2023-28754","record":{"aliases":["GHSA-3cxh-xp3g-jxjm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ShardingSphere Agent","requires_auth":"low_privilege","summary":"Attackers with file write access can execute arbitrary code via malicious YAML deserialization in ShardingSphere Agent.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"shardingsphere","vendor":"apache"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Deserialization of Untrusted Data vulnerability in Apache ShardingSphere-Agent, which allows attackers to execute arbitrary code by constructing a special YAML configuration file.\n\nThe attacker needs to have permission to modify the ShardingSphere Agent YAML configuration file on the target machine, and the target machine can access the URL with the arbitrary code JAR.\nAn attacker can use SnakeYAML to deserialize java.net.URLClassLoader and make it load a JAR from a specified URL, and then deserialize javax.script.ScriptEngineManager to load code using that ClassLoader. When the ShardingSphere JVM process starts and uses the ShardingSphere-Agent, the arbitrary code specified by the attacker will be executed during the deserialization of the YAML configuration file by the Agent.\n\nThis issue affects ShardingSphere-Agent: through 5.3.2. This vulnerability is fixed in Apache ShardingSphere 5.4.0.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ShardingSphere-Agent: Deserialization vulnerability in ShardingSphere Agent","id":"CVE-2023-28754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Ruby URI component ReDoS issue","id":"CVE-2023-28755"},"packages":[{"ecosystem":"Maven","fixed":["5.4.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere","purl":null,"source":"GHSA-3cxh-xp3g-jxjm"},{"ecosystem":"Maven","fixed":["5.4.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere","purl":"pkg:maven/org.apache.shardingsphere/shardingsphere","source":"GHSA-3cxh-xp3g-jxjm"}],"prev":{"headline":"Integer overflow in netconsd","id":"CVE-2023-28753"},"products":["ShardingSphere-Agent"],"published":"2023-07-19","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":9.8,"headline":"Deserialization of Untrusted Data in Apache ShardingSphere","id":"CVE-2020-1947","kev_date_added":null,"published":"2020-03-11"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Apache Software Foundation"]},"summary":"Attackers with file write access can execute arbitrary code via malicious YAML deserialization in ShardingSphere Agent.","url":"https://insights.sbomify.com/CVE-2023-28754/"}