CVE-2022-45347
criticalpriority · track · 40EPSS 0.015 · 74 %ileEUUSEPSS · scored 2026-10-27
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
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
- Maven org.apache.shardingsphere:shardingsphere-proxy< 5.3.0osvUSpkg:maven/org.apache.shardingsphere/shardingsphere-proxy
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-wmxm-6wxc-3xqfApache ShardingSphere-Proxy Incomplete Cleanup vulnerability2022-12-22ghsa · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan