Approved changes feed: RSS · Atom

cpe:2.3:a:apache:shardingsphere:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductShardingsphere (2c37ac67-3cd1-5383-a884-e037a6836a1f)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:apache/shardingsphere purl2cpe 2026-06-01 10:14:28.714874
pkg:github/apache/shardingsphere purl2cpe 2026-06-01 10:14:28.714877
pkg:maven/org.apache.shardingsphere/shardingsphere purl2cpe 2026-06-01 10:14:28.714880
pkg:sourceforge/shardingsphere.mirror purl2cpe 2026-06-01 10:14:28.714883

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-28754 vulnerable 2026-06-08 06:02:35.359781 ShardingSphere-Agent: Deserialization vulnerability in ShardingSphere Agent
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 arbitrary code JAR. An attacker can use SnakeYAML to deserialize java.net.URLClassLoader and make it load a JAR from a specified URL, and then deserialize javax.script.ScriptEngineManager to load code using that ClassLoader. When the ShardingSphere JVM process starts and uses the ShardingSphere-Agent, the arbitrary code specified by the attacker will be executed during the deserialization of the YAML configuration file by the Agent. This issue affects ShardingSphere-Agent: through 5.3.2. This vulnerability is fixed in Apache ShardingSphere 5.4.0.
Published: 2023-07-19T07:15:31.262Z
Updated: 2025-02-13T16:48:51.364Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-45347 vulnerable 2026-06-08 05:50:36.078991 Apache ShardingSphere-Proxy: MySQL authentication bypass
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.
Published: 2022-12-22T10:47:44.716Z
Updated: 2025-04-15T13:41:08.826Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.