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.
References
Link | Resource |
---|---|
https://lists.apache.org/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3l | Mailing List Vendor Advisory |
Configurations
History
29 Dec 2022, 20:05
Type | Values Removed | Values Added |
---|---|---|
References | (MISC) https://lists.apache.org/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3l - Mailing List, Vendor Advisory | |
CPE | cpe:2.3:a:apache:shardingsphere:*:*:*:*:*:*:*:* | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.8 |
First Time |
Apache
Apache shardingsphere |
22 Dec 2022, 11:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2022-12-22 11:15
Updated : 2023-12-10 14:48
NVD link : CVE-2022-45347
Mitre link : CVE-2022-45347
CVE.ORG link : CVE-2022-45347
JSON object : View
Products Affected
apache
- shardingsphere
CWE
CWE-459
Incomplete Cleanup