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.
{ "nvd_published_at": "2022-12-22T11:15:00Z", "github_reviewed_at": "2022-12-22T20:02:29Z", "severity": "CRITICAL", "github_reviewed": true, "cwe_ids": [ "CWE-459" ] }