Overview 6 matches · 3 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
6matches
3in Waratek scope50.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC33.3%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
1
16.7%
No exploit published
2
33.3%
Outside Waratek scope
0
0.0%
Not applicable
3
50.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
6
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
16.7%
Proof of concept only
1
16.7%
Forecast only
0
0.0%
No public exploit
4
66.7%
split by
peak 1 / quarter
Q1 201
Mitigation candidate1
Critical1
not blocked1
Proof of concept only1
Q2 200
Q3 200
Q4 200
Q1 210
Q2 210
Q3 210
Q4 211
Not applicable1
High1
not blocked1
No public exploit1
Q1 221
Not applicable1
Medium1
not blocked1
Working exploit published1
Q2 220
Q3 220
Q4 221
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 230
Q2 230
Q3 231
No exploit published1
High1
not blocked1
No public exploit1
Q4 230
Q1 240
Q2 240
Q3 240
Q4 240
Q1 251
Not applicable1
High1
not blocked1
No public exploit1
Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-31764 | High | 2025-02-06 | Not applicable | No public exploit | The Lite UI of Apache ShardingSphere ElasticJob-UI allows an attacker to perform RCE by constructing a special JDBC URL of H2 database. This issue affects Apache ShardingSphere ElasticJob-UI version 3.0.1 and prior versions. This vulnerability has been fixed in ElasticJob-UI 3.0.2. The premise of this attack is that the attacker has obtained the account and password. Otherwise, the attacker cannot perform this attack. |
| CVE-2023-28754 | High | 2023-07-19 | No exploit published | No public exploit | 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. |
| CVE-2022-45347 | Critical | 2022-12-22 | No exploit published | No public exploit | 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-2022-22733 | Medium | 2022-01-20 | Not applicable | Working exploit published | Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache ShardingSphere ElasticJob-UI allows an attacker who has guest account to do privilege escalation. This issue affects Apache ShardingSphere ElasticJob-UI Apache ShardingSphere ElasticJob-UI 3.x version 3.0.0 and prior versions. |
| CVE-2021-26558 | High | 2021-11-11 | Not applicable | No public exploit | Deserialization of Untrusted Data vulnerability of Apache ShardingSphere-UI allows an attacker to inject outer link resources. This issue affects Apache ShardingSphere-UI Apache ShardingSphere-UI version 4.1.1 and later versions; Apache ShardingSphere-UI versions prior to 5.0.0. |
| CVE-2020-1947 | Critical | 2020-03-11 | Mitigation candidate | Proof of concept only | 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. |