WaratekVRT Sign in
Reset
More filters (2)
Columns
Published to 2002-04-30✕Vendor apache✕
Overview 6 matches · 1 protected · 0 exploited · 0 CISA KEV · 3 public PoC · 1 EPSS ≥ 0.5
Critical 0 0.0% High 0 0.0% Medium 6 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 1 16.7% partly blocked 0 0.0% not blocked 5 83.3% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 3 50.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 3 50.0%
split by peak 2 / quarter
Q3 00Q4 00Q1 01Q2 01Q3 01Q4 01Q1 02
6 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
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-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.