Overview 103 matches · 16 protected · 0 exploited · 0 CISA KEV · 26 public PoC · 13 EPSS ≥ 0.5
Protected by Waratek
16
15.5%
Rule in development
0
0.0%
Mitigation candidate
21
20.4%
No exploit published
66
64.1%
blocked by ARMR today
16
15.5%
partly blocked
0
0.0%
not blocked
87
84.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
26
25.2%
Proof of concept only
0
0.0%
Forecast only
2
1.9%
No public exploit
75
72.8%
split by
peak 14 / year
20001
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20012
Mitigation candidate1
No exploit published1
Medium2
not blocked2
Working exploit published1
No public exploit1
20028
Protected by Waratek1
Mitigation candidate3
No exploit published4
High2
Medium6
blocked by ARMR today1
not blocked7
Working exploit published3
No public exploit5
20037
Protected by Waratek1
Mitigation candidate2
No exploit published4
High1
Medium6
blocked by ARMR today1
not blocked6
Working exploit published3
No public exploit4
20040
20055
Mitigation candidate1
No exploit published4
High1
Medium3
Low1
not blocked5
Working exploit published1
No public exploit4
20061
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
200714
Protected by Waratek1
Mitigation candidate4
No exploit published9
High1
Medium10
Low3
blocked by ARMR today1
not blocked13
Working exploit published5
No public exploit9
20087
Protected by Waratek2
Mitigation candidate2
No exploit published3
Medium7
blocked by ARMR today2
not blocked5
Working exploit published4
No public exploit3
20096
Protected by Waratek1
Mitigation candidate1
No exploit published4
Medium5
Low1
blocked by ARMR today1
not blocked5
Working exploit published1
No public exploit5
20107
Protected by Waratek2
Mitigation candidate2
No exploit published3
Medium6
Low1
blocked by ARMR today2
not blocked5
Working exploit published2
Forecast only1
No public exploit4
201113
Protected by Waratek1
Mitigation candidate1
No exploit published11
High1
Medium10
Low2
blocked by ARMR today1
not blocked12
Working exploit published1
No public exploit12
201212
Mitigation candidate1
No exploit published11
Medium12
not blocked12
Working exploit published1
No public exploit11
20130
201410
Protected by Waratek4
Mitigation candidate1
No exploit published5
High2
Medium8
blocked by ARMR today4
not blocked6
Working exploit published1
No public exploit9
20152
No exploit published2
High1
Medium1
not blocked2
No public exploit2
20166
Protected by Waratek2
No exploit published4
High2
Medium4
blocked by ARMR today2
not blocked4
Forecast only1
No public exploit5
20172
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
Working exploit published1
No public exploit1
200120032005200720092011201320152017
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2001-0917 | Medium | 2001-11-22 | No exploit published | No public exploit | Jakarta Tomcat 4.0.1 allows remote attackers to reveal physical path information by requesting a long URL with a .JSP extension. |
| CVE-2001-0590 | Medium | 2001-08-02 | Mitigation candidate | Working exploit published | Apache Software Foundation Tomcat Servlet prior to 3.2.2 allows a remote attacker to read the source code to arbitrary 'jsp' files via a malformed URL request which does not end with an HTTP protocol specification (i.e. HTTP/1.0). |
| 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. |