Overview 203 matches · 30 protected · 6 exploited · 3 CISA KEV · 60 public PoC · 31 EPSS ≥ 0.5
Protected by Waratek
30
14.8%
Rule in development
0
0.0%
Mitigation candidate
50
24.6%
No exploit published
123
60.6%
blocked by ARMR today
30
14.8%
partly blocked
0
0.0%
not blocked
173
85.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
6
3.0%
Working exploit published
56
27.6%
Proof of concept only
0
0.0%
Forecast only
1
0.5%
No public exploit
140
69.0%
split by
peak 37 / year
20003
Mitigation candidate2
No exploit published1
Medium3
not blocked3
Working exploit published2
No public exploit1
20013
Mitigation candidate1
No exploit published2
High1
Medium2
not blocked3
Working exploit published1
No public exploit2
200212
Protected by Waratek1
Mitigation candidate6
No exploit published5
High3
Medium9
blocked by ARMR today1
not blocked11
Working exploit published6
No public exploit6
20037
Protected by Waratek1
Mitigation candidate2
No exploit published4
High1
Medium6
blocked by ARMR today1
not blocked6
Working exploit published3
No public exploit4
20041
No exploit published1
Medium1
not blocked1
No public exploit1
20059
Protected by Waratek1
Mitigation candidate1
No exploit published7
High1
Medium7
Low1
blocked by ARMR today1
not blocked8
Working exploit published2
No public exploit7
20065
Protected by Waratek3
Mitigation candidate2
High2
Medium3
blocked by ARMR today3
not blocked2
Exploited1
Working exploit published2
No public exploit2
200718
Protected by Waratek2
Mitigation candidate6
No exploit published10
High1
Medium14
Low3
blocked by ARMR today2
not blocked16
Working exploit published7
No public exploit11
20089
Protected by Waratek2
Mitigation candidate2
No exploit published5
Medium9
blocked by ARMR today2
not blocked7
Working exploit published4
No public exploit5
200918
Protected by Waratek3
Mitigation candidate6
No exploit published9
High2
Medium15
Low1
blocked by ARMR today3
not blocked15
Working exploit published8
No public exploit10
201020
Protected by Waratek4
Mitigation candidate5
No exploit published11
Critical1
High1
Medium15
Low3
blocked by ARMR today4
not blocked16
Working exploit published6
Forecast only1
No public exploit13
201120
Protected by Waratek1
Mitigation candidate2
No exploit published17
High2
Medium15
Low3
blocked by ARMR today1
not blocked19
Working exploit published2
No public exploit18
201237
Protected by Waratek2
Mitigation candidate7
No exploit published28
Critical1
High2
Medium33
Low1
blocked by ARMR today2
not blocked35
Exploited1
Working exploit published7
No public exploit29
201334
Protected by Waratek8
Mitigation candidate8
No exploit published18
Critical1
High10
Medium23
blocked by ARMR today8
not blocked26
Exploited4
Working exploit published6
No public exploit24
20147
Protected by Waratek2
No exploit published5
High1
Medium4
Low2
blocked by ARMR today2
not blocked5
No public exploit7
20002002200420062008201020122014
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2000-0760 | Medium | 2000-10-20 | Mitigation candidate | Working exploit published | The Snoop servlet in Jakarta Tomcat 3.1 and 3.0 under Apache reveals sensitive system information when a remote attacker requests a nonexistent URL with a .snp extension. |
| CVE-2000-0759 | Medium | 2000-10-20 | Mitigation candidate | Working exploit published | Jakarta Tomcat 3.1 under Apache reveals physical path information when a remote attacker requests a URL that does not exist, which generates an error message that includes the physical path. |
| CVE-2000-0672 | Medium | 2000-07-20 | No exploit published | No public exploit | The default configuration of Jakarta Tomcat does not restrict access to the /admin context, which allows remote attackers to read arbitrary files by directly calling the administrative servlets to add a context for the root directory. |