CVE-2023-28754
highpriority · track · 36EPSS 0.015 · 73 %ileEUUSEPSS · scored 2026-10-28
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
- Maven org.apache.shardingsphere:shardingsphere< 5.4.0osvUSpkg:maven/org.apache.shardingsphere/shardingsphere
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-3cxh-xp3g-jxjmApache ShardingSphere-Agent Deserialization of Untrusted Data vulnerability2023-07-19ghsa · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2023/07/19/3cnnvd
- https://cxsecurity.com/cveshow/CVE-2023-28754/cnnvd
- https://lists.apache.org/thread/p8onhqox5kkwow9lc6gs03z28wtyp1cgcnnvd
- http://www.openwall.com/lists/oss-security/2023/07/19/3enisa_euvd
- https://lists.apache.org/thread/p8onhqox5kkwow9lc6gs03z28wtyp1cgenisa_euvd
- http://www.openwall.com/lists/oss-security/2023/07/19/3Mailing Listnvd
- https://lists.apache.org/thread/p8onhqox5kkwow9lc6gs03z28wtyp1cgMailing Listnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan