Overview 212 matches · 29 protected · 8 exploited · 5 CISA KEV · 55 public PoC · 35 EPSS ≥ 0.5
Protected by Waratek
31
14.6%
Rule in development
0
0.0%
Mitigation candidate
42
19.8%
No exploit published
139
65.6%
blocked by ARMR today
29
13.7%
partly blocked
2
0.9%
not blocked
181
85.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 22 / year
20003
Mitigation candidate2
No exploit published1
Medium3
not blocked3
Working exploit published2
No public exploit1
20014
Mitigation candidate1
No exploit published3
High1
Medium3
not blocked4
Working exploit published1
No public exploit3
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
20040
20057
Mitigation candidate1
No exploit published6
High1
Medium5
Low1
not blocked7
Working exploit published1
No public exploit6
20061
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
200717
Protected by Waratek2
Mitigation candidate6
No exploit published9
High1
Medium12
Low4
blocked by ARMR today2
not blocked15
Working exploit published7
Proof of concept only1
No public exploit9
20089
Protected by Waratek2
Mitigation candidate2
No exploit published5
Medium9
blocked by ARMR today2
not blocked7
Working exploit published4
No public exploit5
20099
Protected by Waratek1
Mitigation candidate3
No exploit published5
Critical1
High1
Medium5
Low2
blocked by ARMR today1
not blocked8
Exploited1
Working exploit published2
No public exploit6
20108
Protected by Waratek2
Mitigation candidate2
No exploit published4
Medium7
Low1
blocked by ARMR today2
not blocked6
Working exploit published2
Forecast only1
No public exploit5
201115
Protected by Waratek1
Mitigation candidate1
No exploit published13
High1
Medium12
Low2
blocked by ARMR today1
not blocked14
Working exploit published1
No public exploit14
201215
Mitigation candidate1
No exploit published14
Medium14
Low1
not blocked15
Working exploit published1
No public exploit14
20134
Mitigation candidate1
No exploit published3
Medium3
Low1
not blocked4
Working exploit published1
No public exploit3
201413
Protected by Waratek4
Mitigation candidate1
No exploit published8
High2
Medium10
Low1
blocked by ARMR today4
not blocked9
Working exploit published1
No public exploit12
20153
No exploit published3
High1
Medium2
not blocked3
No public exploit3
201612
Protected by Waratek2
Mitigation candidate2
No exploit published8
High8
Medium4
blocked by ARMR today2
not blocked10
Working exploit published2
Forecast only1
No public exploit9
201722
Protected by Waratek5
No exploit published17
Critical4
High15
Medium3
blocked by ARMR today3
partly blocked2
not blocked17
Exploited3
Working exploit published1
Forecast only1
No public exploit17
20188
Mitigation candidate2
No exploit published6
Critical1
High2
Medium5
not blocked8
Working exploit published1
Proof of concept only1
No public exploit6
20197
Protected by Waratek3
Mitigation candidate1
No exploit published3
High5
Medium2
blocked by ARMR today3
not blocked4
Exploited1
Working exploit published1
Forecast only2
No public exploit3
202010
Protected by Waratek2
Mitigation candidate2
No exploit published6
Critical1
High6
Medium3
blocked by ARMR today2
not blocked8
Exploited1
Working exploit published2
Proof of concept only1
Forecast only2
No public exploit4
20218
Protected by Waratek3
No exploit published5
High5
Medium3
blocked by ARMR today3
not blocked5
Forecast only1
No public exploit7
20226
Protected by Waratek2
Mitigation candidate1
No exploit published3
High4
Medium1
Low1
blocked by ARMR today2
not blocked4
Exploited1
Working exploit published1
No public exploit4
202311
Mitigation candidate3
No exploit published8
High6
Medium5
not blocked11
Exploited1
Working exploit published1
Proof of concept only1
No public exploit8
20241
Mitigation candidate1
Medium1
not blocked1
Proof of concept only1
2000200220042006200820102012201420162018202020222024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2002-0936 | Medium | 2002-10-04 | Mitigation candidate | Working exploit published | The Java Server Pages (JSP) engine in Tomcat allows web page owners to cause a denial of service (engine crash) on the web server via a JSP page that calls WPrinterJob().pageSetup(null,null). |
| CVE-2002-0935 | Medium | 2002-10-04 | No exploit published | No public exploit | Apache Tomcat 4.0.3, and possibly other versions before 4.1.3 beta, allows remote attackers to cause a denial of service (resource exhaustion) via a large number of requests to the server with null characters, which causes the working threads to hang. |
| CVE-2002-0493 | High | 2002-08-12 | No exploit published | No public exploit | Apache Tomcat may be started without proper security settings if errors are encountered while reading the web.xml file, which could allow attackers to bypass intended restrictions. |
| CVE-2002-0682 | High | 2002-07-23 | Mitigation candidate | Working exploit published | Cross-site scripting vulnerability in Apache Tomcat 4.0.3 allows remote attackers to execute script as other web users via script in a URL with the /servlet/ mapping, which does not filter the script when an exception is thrown by the servlet. |
| CVE-2000-1210 | Medium | 2002-03-22 | Protected by Waratek | No public exploit | Directory traversal vulnerability in source.jsp of Apache Tomcat before 3.1 allows remote attackers to read arbitrary files via a .. (dot dot) in the argument to source.jsp. |
| CVE-2001-1563 | High | 2001-12-31 | No exploit published | No public exploit | Unknown vulnerability in Tomcat 3.2.1 running on HP Secure OS for Linux 1.0 allows attackers to access servlet resources. NOTE: due to the vagueness of the vendor advisory, it is not clear whether this issue is already covered by other CVE identifiers. |
| CVE-2001-0829 | Medium | 2001-12-06 | No exploit published | No public exploit | A cross-site scripting vulnerability in Apache Tomcat 3.2.1 allows a malicious webmaster to embed Javascript in a request for a .JSP file, which causes the Javascript to be inserted into an error message. |
| 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-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. |