First published: Wed Jul 19 2023(Updated: )
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.
Credit: security@apache.org security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.shardingsphere:shardingsphere | <=5.3.2 | 5.4.0 |
Apache ShardingSphere | <5.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-28754 is a deserialization vulnerability in ShardingSphere Agent that allows attackers to execute arbitrary code by constructing a special YAML configuration file.
CVE-2023-28754 works by exploiting the deserialization of untrusted data in the ShardingSphere Agent, allowing attackers to execute arbitrary code.
CVE-2023-28754 has a severity of 8.8 (high).
ShardingSphere Agent versions up to and including 5.3.2, as well as Apache ShardingSphere versions up to but not including 5.4.0, are affected by CVE-2023-28754.
To mitigate CVE-2023-28754, update ShardingSphere Agent to version 5.4.0 or higher.