ShardingsphereApplication · Apache
CVE-2022-45347
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache ShardingSphere-Proxy prior to 5.3.0 fails to properly clean up database sessions when MySQL client authentication fails. This session cleanup vulnerability allows an attacker using a specially crafted MySQL client to bypass authentication and execute normal database commands, effectively achieving unauthorized database access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ShardingsphereApplication
< 5.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate ShardingSphere-Proxy installation and versionFind the ShardingSphere-Proxy installation directory and identify the version from the release manifest, version file, or jar metadata. Common locations include /opt/shardingsphere-proxy or a custom deployment path.Affected if The installed version is less than 5.3.0 (for example, 5.2.0, 5.1.x, or earlier)
-
Identify if MySQL proxy frontend is configuredExamine the ShardingSphere-Proxy configuration files (typically conf/server.yaml or similar) for database protocol frontend definitions. Look for MySQL-related protocol settings.Affected if The proxy has a MySQL database protocol frontend enabled (for example, proxy_frontend_database_protocol_type: MySQL)
-
Verify the MySQL proxy port exposureCheck the proxy binding configuration in the server configuration file for the port number assigned to MySQL protocol handling and determine if it is bound to a network interface accessible from outside.Affected if The MySQL proxy port is exposed to network segments that are not fully trusted
You are affected if ShardingSphere-Proxy version 5.3.0 or later is NOT installed AND the proxy has a MySQL protocol frontend enabled and accessible to clients.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.3.0
Upgrade Apache ShardingSphere-Proxy to version 5.3.0 or later to obtain the session cleanup fix. If immediate upgrade is not feasible, consider network-level restrictions on proxy access and monitoring for anomalous post-authentication-failure commands.
Apache ShardingSphere-Proxy 5.3.0
- Backup current ShardingSphere-Proxy configuration and data
- Download Apache ShardingSphere-Proxy version 5.3.0 from the official Apache repository
- Stop the running ShardingSphere-Proxy instance
- Upgrade ShardingSphere-Proxy to version 5.3.0
- Review and restore configuration files if needed
- Start the upgraded ShardingSphere-Proxy instance
- Verify the MySQL backend session cleanup is working correctly after authentication failures
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Shardingsphere
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45347 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data