Apache Shardingsphere vulnerabilities

CVE-2023-28754 [HIGH] CWE-502 CVE-2023-28754: Deserialization of Untrusted Data vulnerability in Apache ShardingSphere-Agent, which allows attacke Deserialization of Untrusted Data vulnerability in Apache ShardingSphere-Agent, which allows attackers to execute arbitrary code by constructing a special YAML configuration file. The attacker needs to have permission to modify the ShardingSphere Agent YAML configuration file on the target machine, and the target machine can access the URL with the a

CVE-2022-45347 [CRITICAL] CWE-459 CVE-2022-45347: Apache ShardingSphere-Proxy prior to 5.3.0 when using MySQL as database backend didn't cleanup the d 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.

CVE-2020-1947 [CRITICAL] CWE-502 CVE-2020-1947: In Apache ShardingSphere(incubator) 4.0.0-RC3 and 4.0.0, the ShardingSphere's web console uses the S In Apache ShardingSphere(incubator) 4.0.0-RC3 and 4.0.0, the ShardingSphere's web console uses the SnakeYAML library for parsing YAML inputs to load datasource configuration. SnakeYAML allows to unmarshal data to a Java type By using the YAML tag. Unmarshalling untrusted data can lead to security flaws of RCE.