Overview 223 matches · 207 in Waratek scope · 29 protected · 8 exploited · 5 CISA KEV · 47 public PoC · 31 EPSS ≥ 0.5
223matches
207in Waratek scope92.8%
29protected13.0%
8exploited3.6%
5CISA KEV2.2%
47public PoC21.1%
31EPSS ≥ 0.513.9%
Protected by Waratek
30
13.5%
Rule in development
0
0.0%
Mitigation candidate
32
14.3%
No exploit published
145
65.0%
Outside Waratek scope
15
6.7%
Not applicable
1
0.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
29
13.0%
partly blocked
1
0.4%
not blocked
193
86.5%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 31 / year
20001
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20013
Mitigation candidate1
No exploit published1
Outside Waratek scope1
Medium3
not blocked3
Working exploit published1
No public exploit2
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
200715
Protected by Waratek1
Mitigation candidate4
No exploit published9
Outside Waratek scope1
High1
Medium11
Low3
blocked by ARMR today1
not blocked14
Working exploit published6
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
20097
Protected by Waratek1
Mitigation candidate1
No exploit published4
Not applicable1
Critical1
Medium5
Low1
blocked by ARMR today1
not blocked6
Exploited1
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
20133
Outside Waratek scope3
Medium2
Low1
not blocked3
No public exploit3
201412
Protected by Waratek4
Mitigation candidate1
No exploit published5
Outside Waratek scope2
High2
Medium10
blocked by ARMR today4
not blocked8
Working exploit published1
No public exploit11
20153
No exploit published2
Outside Waratek scope1
High1
Medium2
not blocked3
No public exploit3
20168
Protected by Waratek2
No exploit published4
Outside Waratek scope2
High4
Medium4
blocked by ARMR today2
not blocked6
Forecast only1
No public exploit7
201719
Protected by Waratek4
No exploit published13
Outside Waratek scope2
Critical4
High12
Medium3
blocked by ARMR today3
partly blocked1
not blocked15
Exploited2
Working exploit published1
Forecast only1
No public exploit15
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20192
Mitigation candidate1
No exploit published1
High1
Medium1
not blocked2
Working exploit published1
Forecast only1
20209
Protected by Waratek1
Mitigation candidate2
No exploit published5
Outside Waratek scope1
High6
Medium3
blocked by ARMR today1
not blocked8
Working exploit published2
Proof of concept only1
Forecast only2
No public exploit4
20216
Protected by Waratek2
No exploit published4
High4
Medium2
blocked by ARMR today2
not blocked4
Forecast only1
No public exploit5
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
202411
Mitigation candidate4
No exploit published7
Critical3
High3
Medium5
not blocked11
Exploited1
Proof of concept only3
No public exploit7
202515
Protected by Waratek4
No exploit published9
Outside Waratek scope2
Critical3
High10
Medium2
blocked by ARMR today4
not blocked11
Exploited1
Working exploit published1
Proof of concept only1
No public exploit12
202631
Protected by Waratek2
No exploit published29
Critical11
High12
Medium7
Low1
blocked by ARMR today2
not blocked29
Exploited1
Working exploit published1
No public exploit29
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2005-4703 | Medium | 2005-12-31 | Mitigation candidate | Working exploit published | Apache Tomcat 4.0.3, when running on Windows, allows remote attackers to obtain sensitive information via a request for a file that contains an MS-DOS device name such as lpt9, which leaks the pathname in an error message, as demonstrated by lpt9.xtp using Nikto. |
| CVE-2005-3510 | Medium | 2005-11-06 | No exploit published | No public exploit | Apache Tomcat 5.5.0 to 5.5.11 allows remote attackers to cause a denial of service (CPU consumption) via a large number of simultaneous requests to list a web directory that has a large number of files. |
| CVE-2005-3164 | Low | 2005-10-06 | No exploit published | No public exploit | The AJP connector in Apache Tomcat 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standalone, does not properly handle when a connection is broken before request body data is sent in a POST request, which can lead to an information leak when "unsuitable request body data" is used for a different request, possibly related to Java Servlet pages. |
| CVE-2005-2090 | Medium | 2005-07-05 | No exploit published | No public exploit | Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling." |
| CVE-2003-0866 | Medium | 2003-11-17 | Mitigation candidate | Working exploit published | The Catalina org.apache.catalina.connector.http package in Tomcat 4.0.x up to 4.0.3 allows remote attackers to cause a denial of service via several requests that do not follow the HTTP protocol, which causes Tomcat to reject later requests. |
| 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-0829 | Medium | 2001-12-06 | Outside Waratek scope | 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-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. |