Overview 120 matches · 18 protected · 1 exploited · 1 CISA KEV · 42 public PoC · 18 EPSS ≥ 0.5
Protected by Waratek
18
15.0%
Rule in development
0
0.0%
Mitigation candidate
34
28.3%
No exploit published
68
56.7%
blocked by ARMR today
18
15.0%
partly blocked
0
0.0%
not blocked
102
85.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
0.8%
Working exploit published
42
35.0%
Proof of concept only
0
0.0%
Forecast only
1
0.8%
No public exploit
76
63.3%
split by
peak 20 / 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
201115
Protected by Waratek1
Mitigation candidate1
No exploit published13
Medium12
Low3
blocked by ARMR today1
not blocked14
Working exploit published1
No public exploit14
200020012002200320042005200620072008200920102011
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2003-0042 | Medium | 2003-02-07 | Protected by Waratek | Working exploit published | Jakarta Tomcat before 3.3.1a, when used with JDK 1.3.1 or earlier, allows remote attackers to list directories even with an index.html or other file present, or obtain unprocessed source code for a JSP file, via a URL containing a null character. |
| CVE-2002-1394 | High | 2003-01-17 | No exploit published | No public exploit | Apache Tomcat 4.0.5 and earlier, when using both the invoker servlet and the default servlet, allows remote attackers to read source code for server files or bypass certain protections, a variant of CAN-2002-1148. |
| CVE-2002-2272 | High | 2002-12-31 | Mitigation candidate | Working exploit published | Tomcat 4.0 through 4.1.12, using mod_jk 1.2.1 module on Apache 1.3 through 1.3.27, allows remote attackers to cause a denial of service (desynchronized communications) via an HTTP GET request with a Transfer-Encoding chunked field with invalid values. |
| CVE-2002-2009 | Medium | 2002-12-31 | No exploit published | No public exploit | Apache Tomcat 4.0.1 allows remote attackers to obtain the web root path via HTTP requests for JSP files preceded by (1) +/, (2) >/, (3) </, and (4) %20/, which leaks the pathname in an error message. |
| CVE-2002-2008 | Medium | 2002-12-31 | No exploit published | No public exploit | Apache Tomcat 4.0.3 for Windows allows remote attackers to obtain the web root path via an HTTP request for a resource that does not exist, such as lpt9, which leaks the information in an error message. |
| CVE-2002-2007 | Medium | 2002-12-31 | Mitigation candidate | Working exploit published | The default installations of Apache Tomcat 3.2.3 and 3.2.4 allows remote attackers to obtain sensitive system information such as directory listings and web root path, via erroneous HTTP requests for Java Server Pages (JSP) in the (1) test/jsp, (2) samples/jsp and (3) examples/jsp directories, or the (4) test/realPath.jsp servlet, which leaks pathnames in error messages. |
| CVE-2002-2006 | Medium | 2002-12-31 | Mitigation candidate | Working exploit published | The default installation of Apache Tomcat 4.0 through 4.1 and 3.0 through 3.3.1 allows remote attackers to obtain the installation path and other sensitive system information via the (1) SnoopServlet or (2) TroubleShooter example servlets. |
| CVE-2002-1895 | Medium | 2002-12-31 | No exploit published | No public exploit | The servlet engine in Jakarta Apache Tomcat 3.3 and 4.0.4, when using IIS and the ajp1.3 connector, allows remote attackers to cause a denial of service (crash) via a large number of HTTP GET requests for an MS-DOS device such as AUX, LPT1, CON, or PRN. |
| CVE-2002-1148 | Medium | 2002-10-11 | Mitigation candidate | Working exploit published | The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet. |
| 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-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. |