Overview 102 matches · 47 protected · 24 CISA KEV · 75 public PoC · 39 EPSS ≥ 0.5
Protected by Waratek
50
49.0%
Rule in development
3
2.9%
Mitigation candidate
49
48.0%
No exploit published
0
0.0%
blocked by ARMR today
47
46.1%
partly blocked
3
2.9%
not blocked
47
46.1%
not established
5
4.9%
unrecorded
0
0.0%
Exploited
102
100.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 11 / quarter
Q4 222
Protected by Waratek2
Critical1
High1
blocked by ARMR today2
Exploited2
Q1 235
Protected by Waratek4
Mitigation candidate1
Critical2
High3
blocked by ARMR today4
not blocked1
Exploited5
Q2 236
Protected by Waratek4
Mitigation candidate2
Critical2
High4
blocked by ARMR today4
not blocked1
not established1
Exploited6
Q3 234
Protected by Waratek2
Mitigation candidate2
Critical3
High1
blocked by ARMR today2
not blocked2
Exploited4
Q4 237
Protected by Waratek1
Mitigation candidate6
Critical5
High2
blocked by ARMR today1
not blocked5
not established1
Exploited7
Q1 249
Protected by Waratek2
Mitigation candidate7
Critical4
High4
Medium1
blocked by ARMR today2
not blocked7
Exploited9
Q2 246
Protected by Waratek4
Mitigation candidate2
Critical3
High3
blocked by ARMR today4
not blocked2
Exploited6
Q3 245
Protected by Waratek4
Mitigation candidate1
Critical1
High3
Medium1
blocked by ARMR today3
partly blocked1
not blocked1
Exploited5
Q4 244
Protected by Waratek3
Mitigation candidate1
Critical3
High1
blocked by ARMR today3
not blocked1
Exploited4
Q1 256
Protected by Waratek3
Mitigation candidate3
Critical3
High1
Medium2
blocked by ARMR today3
not blocked3
Exploited6
Q2 258
Protected by Waratek2
Rule in development1
Mitigation candidate5
Critical3
High2
Medium3
blocked by ARMR today2
not blocked6
Exploited8
Q3 258
Protected by Waratek3
Rule in development1
Mitigation candidate4
Critical5
High1
Medium2
blocked by ARMR today3
not blocked5
Exploited8
Q4 259
Protected by Waratek3
Rule in development1
Mitigation candidate5
Critical6
High2
Medium1
blocked by ARMR today3
not blocked4
not established2
Exploited9
Q1 263
Protected by Waratek2
Mitigation candidate1
Critical2
High1
blocked by ARMR today2
not established1
Exploited3
Q2 2611
Protected by Waratek6
Mitigation candidate5
Critical6
High5
blocked by ARMR today6
not blocked5
Exploited11
Q3 266
Protected by Waratek2
Mitigation candidate4
Critical5
High1
blocked by ARMR today1
partly blocked1
not blocked4
Exploited6
Q4 263
Protected by Waratek3
Critical2
High1
blocked by ARMR today2
partly blocked1
Exploited3
Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-10650 | High | 2022-12-26 | Protected by Waratek | Exploited | A deserialization flaw was discovered in jackson-databind through 2.9.10.4. It could allow an unauthenticated user to perform code execution via ignite-jta or quartz-core: org.apache.ignite.cache.jta.jndi.CacheJndiTmLookup, org.apache.ignite.cache.jta.jndi.CacheJndiTmFactory, and org.quartz.utils.JNDIConnectionProvider. |
| CVE-2022-1471 | Critical | 2022-12-01 | Protected by Waratek | Exploited | SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond. |