{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.shardingsphere:shardingsphere-proxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45347 in the wild and no public exploit code.","fix":"Upgrade org.apache.shardingsphere:shardingsphere-proxy to 5.3.0 or later.","what":"CVE-2022-45347 is a critical authentication bypass vulnerability in Apache ShardingSphere-Proxy, published on 22 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45347 and fix it if it is affected.\n\nWhat it is: CVE-2022-45347 is a critical authentication bypass vulnerability in Apache ShardingSphere-Proxy, published on 22 Dec 2022. 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-2022-45347 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.shardingsphere:shardingsphere-proxy (Maven): affected all versions; fixed in 5.3.0\n- org.apache.shardingsphere:shardingsphere-proxy (Maven): affected all versions; fixed in 5.3.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-2022-45347/ (Markdown: https://insights.sbomify.com/CVE-2022-45347/index.md)","id":"CVE-2022-45347","markdown":"https://insights.sbomify.com/CVE-2022-45347/index.md","name":"CVE-2022-45347","record":{"aliases":["GHSA-wmxm-6wxc-3xqf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Database proxy server","requires_auth":"none","summary":"Attackers can bypass MySQL authentication in Apache ShardingSphere-Proxy to execute commands and access data due to incomplete session cleanup.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"shardingsphere","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-459","name":"Incomplete Cleanup"}],"description":"Apache ShardingSphere-Proxy prior to 5.3.0 when using MySQL as database backend didn't cleanup the database session completely after client authentication failed, which allowed an attacker to execute normal commands by constructing a special MySQL client. This vulnerability has been fixed in Apache ShardingSphere 5.3.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":"Apache ShardingSphere-Proxy: MySQL authentication bypass","id":"CVE-2022-45347","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"WordPress amr users Plugin \u003c= 4.59.4 is vulnerable to CSV Injection","id":"CVE-2022-45348"},"packages":[{"ecosystem":"Maven","fixed":["5.3.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere-proxy","purl":null,"source":"GHSA-wmxm-6wxc-3xqf"},{"ecosystem":"Maven","fixed":["5.3.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.shardingsphere:shardingsphere-proxy","purl":"pkg:maven/org.apache.shardingsphere/shardingsphere-proxy","source":"GHSA-wmxm-6wxc-3xqf"}],"prev":{"headline":"Use after free in n/a","id":"CVE-2022-45343"},"products":["Apache ShardingSphere-Proxy"],"published":"2022-12-22","related":[{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Apache ShardingSphere","id":"CVE-2020-1947","kev_date_added":null,"published":"2020-03-11"},{"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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass MySQL authentication in Apache ShardingSphere-Proxy to execute commands and access data due to incomplete session cleanup.","url":"https://insights.sbomify.com/CVE-2022-45347/"}