Overview 206 matches · 0 protected · 26 exploited · 2 CISA KEV · 193 public PoC · 52 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
206
100.0%
No exploit published
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
201
97.6%
not established
5
2.4%
unrecorded
0
0.0%
split by
peak 24 / year
20006
Mitigation candidate6
High2
Medium4
not blocked6
Working exploit published6
20012
Mitigation candidate2
Medium2
not blocked2
Working exploit published2
20028
Mitigation candidate8
High2
Medium6
not blocked8
Working exploit published8
20037
Mitigation candidate7
High2
Medium4
Low1
not blocked7
Working exploit published7
20041
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20054
Mitigation candidate4
Medium4
not blocked4
Working exploit published4
20064
Mitigation candidate4
Medium4
not blocked4
Working exploit published4
200710
Mitigation candidate10
High1
Medium9
not blocked10
Working exploit published10
20089
Mitigation candidate9
High1
Medium8
not blocked9
Working exploit published9
200913
Mitigation candidate13
High4
Medium9
not blocked13
Exploited1
Working exploit published12
201012
Mitigation candidate12
High1
Medium9
Low2
not blocked12
Exploited1
Working exploit published11
20119
Mitigation candidate9
High4
Medium3
Low2
not blocked9
Working exploit published9
201224
Mitigation candidate24
Critical1
High2
Medium17
Low4
not blocked22
not established2
Exploited5
Working exploit published19
201318
Mitigation candidate18
High4
Medium12
Low2
not blocked17
not established1
Exploited3
Working exploit published14
No public exploit1
201412
Mitigation candidate12
High3
Medium9
not blocked12
Exploited2
Working exploit published10
20156
Mitigation candidate6
High1
Medium1
Low4
not blocked6
Exploited1
Working exploit published4
Proof of concept only1
201612
Mitigation candidate12
Critical1
High7
Medium4
not blocked11
not established1
Exploited1
Working exploit published11
201714
Mitigation candidate14
Critical5
High4
Medium5
not blocked14
Exploited4
Working exploit published8
Proof of concept only2
201816
Mitigation candidate16
Critical1
High7
Medium8
not blocked16
Exploited3
Working exploit published12
Proof of concept only1
201919
Mitigation candidate19
High7
Medium12
not blocked18
not established1
Exploited5
Working exploit published14
2001200320052007200920112013201520172019
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-0685 | High | 2000-10-20 | Mitigation candidate | Working exploit published | BEA WebLogic 5.1.x does not properly restrict access to the PageCompileServlet, which could allow remote attackers to compile and execute Java JHTML code by directly invoking the servlet on any source file. |
| CVE-2000-0684 | High | 2000-10-20 | Mitigation candidate | Working exploit published | BEA WebLogic 5.1.x does not properly restrict access to the JSPServlet, which could allow remote attackers to compile and execute Java JSP code by directly invoking the servlet on any source file. |
| CVE-2000-0652 | Medium | 2000-07-24 | Mitigation candidate | Working exploit published | IBM WebSphere allows remote attackers to read source code for executable web files by directly calling the default InvokerServlet using a URL which contains the "/servlet/file" string. |
| CVE-2000-0500 | Medium | 2000-06-21 | Mitigation candidate | Working exploit published | The default configuration of BEA WebLogic 5.1.0 allows a remote attacker to view source code of programs by requesting a URL beginning with /file/, which causes the default servlet to display the file without further processing. |