Overview 204 matches · 0 in Waratek scope · 0 protected · 3 exploited · 1 CISA KEV · 28 public PoC · 8 EPSS ≥ 0.5
204matches
0in Waratek scope0.0%
0protected0.0%
3exploited1.5%
1CISA KEV0.5%
28public PoC13.7%
8EPSS ≥ 0.53.9%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
27
13.2%
Not applicable
177
86.8%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
204
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 60 / year
19981
Not applicable1
High1
not blocked1
No public exploit1
19994
Not applicable4
Medium4
not blocked4
Working exploit published2
No public exploit2
20009
Not applicable9
High4
Medium5
not blocked9
Working exploit published4
No public exploit5
20013
Not applicable3
High2
Medium1
not blocked3
Working exploit published3
20022
Not applicable2
High2
not blocked2
No public exploit2
20032
Not applicable2
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
20044
Not applicable4
High2
Medium2
not blocked4
Working exploit published1
No public exploit3
20052
Not applicable2
Medium2
not blocked2
No public exploit2
20063
Not applicable3
High2
Medium1
not blocked3
Working exploit published2
No public exploit1
20073
Not applicable3
High1
Medium2
not blocked3
Exploited1
No public exploit2
20087
Not applicable7
High7
not blocked7
Working exploit published2
No public exploit5
20094
Not applicable4
Medium4
not blocked4
No public exploit4
20102
Not applicable2
High2
not blocked2
No public exploit2
20110
20121
Not applicable1
High1
not blocked1
No public exploit1
20131
Not applicable1
Medium1
not blocked1
No public exploit1
20148
Not applicable8
High5
Medium3
not blocked8
Exploited1
Proof of concept only1
No public exploit6
20154
Not applicable4
Medium3
Low1
not blocked4
No public exploit4
20169
Outside Waratek scope1
Not applicable8
High7
Medium2
not blocked9
Working exploit published2
No public exploit7
201760
Outside Waratek scope18
Not applicable42
Critical3
High25
Medium30
Low2
not blocked60
Working exploit published2
Forecast only1
No public exploit57
20187
Outside Waratek scope5
Not applicable2
Critical2
High3
Medium2
not blocked7
Working exploit published2
No public exploit5
20198
Not applicable8
Critical4
High2
Medium2
not blocked8
Exploited1
Working exploit published3
No public exploit4
20208
Outside Waratek scope3
Not applicable5
Critical2
High2
Medium4
not blocked8
No public exploit8
20213
Not applicable3
High1
Medium2
not blocked3
No public exploit3
20220
202321
Not applicable21
Critical1
High9
Medium11
not blocked21
Proof of concept only7
No public exploit14
202423
Not applicable23
Critical3
High6
Medium14
not blocked23
Proof of concept only3
No public exploit20
20254
Not applicable4
High2
Medium2
not blocked4
Proof of concept only2
No public exploit2
20261
Not applicable1
Medium1
not blocked1
No public exploit1
1999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-1999-1052 | Medium | 1999-08-24 | Not applicable | No public exploit | Microsoft FrontPage stores form results in a default location in /_private/form_results.txt, which is world-readable and accessible in the document root, which allows remote attackers to read possibly sensitive information submitted by other users. |
| CVE-2000-0153 | Medium | 1999-03-26 | Not applicable | No public exploit | FrontPage Personal Web Server (PWS) allows remote attackers to read files via a .... (dot dot) attack. |
| CVE-1999-0386 | Medium | 1999-03-01 | Not applicable | Working exploit published | Microsoft Personal Web Server and FrontPage Personal Web Server in some Windows systems allows a remote attacker to read files on the server by using a nonstandard URL. |
| CVE-1999-0012 | High | 1998-02-06 | Not applicable | No public exploit | Some web servers under Microsoft Windows allow remote attackers to bypass access restrictions for files with long file names. |