Overview 202 matches · 44 protected · 21 exploited · 8 CISA KEV · 69 EPSS ≥ 0.5
Protected by Waratek
44
21.8%
Rule in development
0
0.0%
Mitigation candidate
158
78.2%
No exploit published
0
0.0%
blocked by ARMR today
44
21.8%
partly blocked
0
0.0%
not blocked
158
78.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
21
10.4%
Working exploit published
176
87.1%
Proof of concept only
5
2.5%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 24 / year
20007
Mitigation candidate7
High3
Medium4
not blocked7
Working exploit published7
20014
Mitigation candidate4
High1
Medium3
not blocked4
Working exploit published4
20028
Mitigation candidate8
High2
Medium6
not blocked8
Working exploit published8
20039
Protected by Waratek1
Mitigation candidate8
High2
Medium6
Low1
blocked by ARMR today1
not blocked8
Working exploit published9
20042
Protected by Waratek1
Mitigation candidate1
High1
Medium1
blocked by ARMR today1
not blocked1
Working exploit published2
20056
Protected by Waratek1
Mitigation candidate5
High1
Medium5
blocked by ARMR today1
not blocked5
Working exploit published6
20066
Protected by Waratek1
Mitigation candidate5
High1
Medium5
blocked by ARMR today1
not blocked5
Working exploit published6
200715
Protected by Waratek2
Mitigation candidate13
High1
Medium12
Low2
blocked by ARMR today2
not blocked13
Working exploit published14
Proof of concept only1
200815
Protected by Waratek4
Mitigation candidate11
High4
Medium11
blocked by ARMR today4
not blocked11
Exploited1
Working exploit published14
200920
Protected by Waratek4
Mitigation candidate16
Critical1
High7
Medium11
Low1
blocked by ARMR today4
not blocked16
Exploited2
Working exploit published18
201018
Protected by Waratek5
Mitigation candidate13
High3
Medium13
Low2
blocked by ARMR today5
not blocked13
Exploited3
Working exploit published15
201116
Protected by Waratek3
Mitigation candidate13
High8
Medium6
Low2
blocked by ARMR today3
not blocked13
Working exploit published15
Proof of concept only1
201224
Protected by Waratek3
Mitigation candidate21
Critical2
High1
Medium17
Low4
blocked by ARMR today3
not blocked21
Exploited3
Working exploit published21
201323
Protected by Waratek7
Mitigation candidate16
Critical1
High6
Medium15
Low1
blocked by ARMR today7
not blocked16
Exploited5
Working exploit published17
Proof of concept only1
201420
Protected by Waratek7
Mitigation candidate13
High7
Medium13
blocked by ARMR today7
not blocked13
Exploited5
Working exploit published14
Proof of concept only1
20159
Protected by Waratek5
Mitigation candidate4
Critical1
High1
Medium5
Low2
blocked by ARMR today5
not blocked4
Exploited2
Working exploit published6
Proof of concept only1
20012003200520072009201120132015
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |