Overview 117 matches · 18 protected · 1 exploited · 1 CISA KEV · 27 public PoC · 15 EPSS ≥ 0.5
Protected by Waratek
18
15.4%
Rule in development
0
0.0%
Mitigation candidate
21
17.9%
No exploit published
78
66.7%
blocked by ARMR today
18
15.4%
partly blocked
0
0.0%
not blocked
99
84.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
0.9%
Working exploit published
26
22.2%
Proof of concept only
0
0.0%
Forecast only
3
2.6%
No public exploit
87
74.4%
split by
peak 16 / 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
201716
Protected by Waratek3
No exploit published13
Critical4
High10
Medium2
blocked by ARMR today3
not blocked13
Exploited1
Working exploit published1
Forecast only1
No public exploit13
200120032005200720092011201320152017
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2002-1567 | Medium | 2003-10-06 | Mitigation candidate | Working exploit published | Cross-site scripting (XSS) vulnerability in Apache Tomcat 4.1 allows remote attackers to execute arbitrary web script and steal cookies via a URL with encoded newlines followed by a request to a .jsp file whose name contains the script. |
| CVE-2003-0045 | Medium | 2003-02-07 | No exploit published | No public exploit | Jakarta Tomcat before 3.3.1a on certain Windows systems may allow remote attackers to cause a denial of service (thread hang and resource consumption) via a request for a JSP page containing an MS-DOS device name, such as aux.jsp. |
| CVE-2003-0044 | Medium | 2003-02-07 | No exploit published | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in the (1) examples and (2) ROOT web applications for Jakarta Tomcat 3.x through 3.3.1a allow remote attackers to insert arbitrary web script or HTML. |
| CVE-2003-0043 | Medium | 2003-02-07 | No exploit published | No public exploit | Jakarta Tomcat before 3.3.1a, when used with JDK 1.3.1 or earlier, uses trusted privileges when processing the web.xml file, which could allow remote attackers to read portions of some files through the web.xml file. |
| 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-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-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-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-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-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. |