CVE-2022-45347 json
Apache ShardingSphere-Proxy: MySQL authentication bypass
published 2022-12-22 3 y ago modified 2026-06-17 4 mo ago also GHSA-wmxm-6wxc-3xqf , EUVD-2022-7763
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.shardingsphere:shardingsphere-proxy 5.3.0
- Apache Software Foundation Apache ShardingSphere-Proxy 5.3.0
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.shardingsphere:shardingsphere-proxy | <5.3.0 |
5.3.0 |
Affected products
- Apache Software Foundation Apache ShardingSphere-Proxy
Classification
- Weakness
-
- CWE-459 Incomplete Cleanup
References
-
lists.apache.org
/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3l
vendor-advisory, web, mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2022-45347
advisory
-
github.com
/pjfanning/shardingsphere
package
Sources
- CVE List CVE-2022-45347
- GitHub Advisory GHSA-wmxm-6wxc-3xqf
- NVD CVE-2022-45347
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.