Overview 101 matches · 39 protected · 43 exploited · 23 CISA KEV · 59 public PoC
Protected by Waratek
41
40.6%
Rule in development
1
1.0%
Mitigation candidate
26
25.7%
No exploit published
33
32.7%
blocked by ARMR today
39
38.6%
partly blocked
2
2.0%
not blocked
60
59.4%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
43
42.6%
Working exploit published
14
13.9%
Proof of concept only
17
16.8%
Forecast only
27
26.7%
No public exploit
0
0.0%
split by
peak 17 / quarter
Q3 2213
Protected by Waratek2
Mitigation candidate1
No exploit published10
Critical5
High4
Medium4
blocked by ARMR today2
not blocked11
Exploited2
Proof of concept only6
Forecast only5
Q4 225
Protected by Waratek5
Critical4
High1
blocked by ARMR today5
Exploited3
Forecast only2
Q1 236
Protected by Waratek2
Mitigation candidate1
No exploit published3
Critical3
High2
Medium1
blocked by ARMR today2
not blocked4
Exploited3
Forecast only3
Q2 2317
Protected by Waratek6
Mitigation candidate2
No exploit published9
Critical9
High6
Medium2
blocked by ARMR today6
not blocked11
Exploited3
Working exploit published2
Proof of concept only6
Forecast only6
Q3 234
Protected by Waratek1
Mitigation candidate2
No exploit published1
Critical3
High1
blocked by ARMR today1
not blocked3
Exploited2
Working exploit published1
Forecast only1
Q4 2312
Protected by Waratek2
Mitigation candidate7
No exploit published3
Critical6
High5
Medium1
blocked by ARMR today2
not blocked10
Exploited4
Working exploit published4
Proof of concept only2
Forecast only2
Q1 248
Protected by Waratek3
Mitigation candidate3
No exploit published2
Critical3
High3
Medium2
blocked by ARMR today3
not blocked5
Exploited3
Working exploit published1
Proof of concept only1
Forecast only3
Q2 246
Protected by Waratek2
No exploit published4
Critical5
Medium1
blocked by ARMR today2
not blocked4
Exploited2
Proof of concept only1
Forecast only3
Q3 243
Protected by Waratek3
Critical2
High1
blocked by ARMR today1
partly blocked2
Exploited2
Working exploit published1
Q4 245
Protected by Waratek2
Mitigation candidate2
No exploit published1
Critical3
High2
blocked by ARMR today2
not blocked3
Exploited2
Working exploit published2
Forecast only1
Q1 255
Protected by Waratek3
Mitigation candidate2
Critical3
Medium2
blocked by ARMR today3
not blocked2
Exploited4
Forecast only1
Q2 254
Protected by Waratek1
Mitigation candidate3
Critical2
High2
blocked by ARMR today1
not blocked3
Exploited2
Working exploit published2
Q3 251
Mitigation candidate1
Critical1
not blocked1
Exploited1
Q4 256
Protected by Waratek4
Rule in development1
Mitigation candidate1
Critical4
High2
blocked by ARMR today4
not blocked2
Exploited4
Working exploit published1
Proof of concept only1
Q1 261
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Q2 264
Protected by Waratek4
Critical1
High3
blocked by ARMR today4
Exploited4
Q3 261
Mitigation candidate1
Critical1
not blocked1
Exploited1
Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25Q3 25Q1 26Q3 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-33891 | High | 2022-07-18 | Protected by Waratek | Exploited | The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1. |