Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Shardingsphere | < 5.3.0 |
Related Weaknesses (CWE)
References
- https://lists.apache.org/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3lMailing ListVendor Advisory
- https://lists.apache.org/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3lMailing ListVendor Advisory
FAQ
What is CVE-2022-45347?
CVE-2022-45347 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 ...
How severe is CVE-2022-45347?
CVE-2022-45347 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2022-45347?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Shardingsphere.