Overview 203 matches · 56 protected · 23 exploited · 12 CISA KEV · 73 EPSS ≥ 0.5
Protected by Waratek
58
28.6%
Rule in development
0
0.0%
Mitigation candidate
145
71.4%
No exploit published
0
0.0%
blocked by ARMR today
56
27.6%
partly blocked
2
1.0%
not blocked
145
71.4%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
23
11.3%
Working exploit published
175
86.2%
Proof of concept only
5
2.5%
Forecast only
0
0.0%
No public exploit
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
20038
Protected by Waratek1
Mitigation candidate7
High2
Medium5
Low1
blocked by ARMR today1
not blocked7
Working exploit published8
20041
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20055
Protected by Waratek1
Mitigation candidate4
Medium5
blocked by ARMR today1
not blocked4
Working exploit published5
20065
Protected by Waratek1
Mitigation candidate4
Medium5
blocked by ARMR today1
not blocked4
Working exploit published5
200711
Protected by Waratek1
Mitigation candidate10
High1
Medium9
Low1
blocked by ARMR today1
not blocked10
Working exploit published11
200813
Protected by Waratek4
Mitigation candidate9
High2
Medium11
blocked by ARMR today4
not blocked9
Exploited1
Working exploit published12
200917
Protected by Waratek4
Mitigation candidate13
High5
Medium11
Low1
blocked by ARMR today4
not blocked13
Exploited1
Working exploit published16
201016
Protected by Waratek5
Mitigation candidate11
High2
Medium12
Low2
blocked by ARMR today5
not blocked11
Exploited2
Working exploit published14
201112
Protected by Waratek3
Mitigation candidate9
High5
Medium5
Low2
blocked by ARMR today3
not blocked9
Working exploit published11
Proof of concept only1
201222
Protected by Waratek3
Mitigation candidate19
Critical2
High1
Medium15
Low4
blocked by ARMR today3
not blocked19
Exploited3
Working exploit published19
201322
Protected by Waratek7
Mitigation candidate15
Critical1
High6
Medium14
Low1
blocked by ARMR today7
not blocked15
Exploited4
Working exploit published17
Proof of concept only1
201419
Protected by Waratek7
Mitigation candidate12
High6
Medium13
blocked by ARMR today7
not blocked12
Exploited4
Working exploit published14
Proof of concept only1
201512
Protected by Waratek7
Mitigation candidate5
Critical3
High1
Medium4
Low4
blocked by ARMR today7
not blocked5
Exploited3
Working exploit published8
Proof of concept only1
201624
Protected by Waratek14
Mitigation candidate10
Critical7
High12
Medium5
blocked by ARMR today12
partly blocked2
not blocked10
Exploited5
Working exploit published18
Proof of concept only1
200020022004200620082010201220142016
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |