Overview 3 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
3matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
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
0
0.0%
Not applicable
3
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
3
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
3
100.0%
split by
peak 1 / quarter
Q4 021
Not applicable1
High1
not blocked1
No public exploit1
Q1 030
Q2 030
Q3 030
Q4 030
Q1 040
Q2 040
Q3 040
Q4 041
Not applicable1
High1
not blocked1
No public exploit1
Q1 050
Q2 050
Q3 050
Q4 050
Q1 060
Q2 060
Q3 060
Q4 060
Q1 070
Q2 070
Q3 070
Q4 071
Not applicable1
High1
not blocked1
No public exploit1
Q4 02Q2 03Q4 03Q2 04Q4 04Q2 05Q4 05Q2 06Q4 06Q2 07Q4 07
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2007-5969 | High | 2007-12-10 | Not applicable | No public exploit | MySQL Community Server 5.0.x before 5.0.51, Enterprise Server 5.0.x before 5.0.52, Server 5.1.x before 5.1.23, and Server 6.0.x before 6.0.4, when a table relies on symlinks created through explicit DATA DIRECTORY and INDEX DIRECTORY options, allows remote authenticated users to overwrite system table information and gain privileges via a RENAME TABLE statement that changes the symlink to point to an existing file. |
| CVE-2004-1322 | High | 2004-12-15 | Not applicable | No public exploit | Cisco Unity 2.x, 3.x, and 4.x, when integrated with Microsoft Exchange, has several hard coded usernames and passwords, which allows remote attackers to gain unauthorized access and change configuration settings or read outgoing or incoming e-mail messages. |
| CVE-2002-1190 | High | 2002-10-28 | Not applicable | No public exploit | Cisco Unity 2.x and 3.x uses well-known default user accounts, which could allow remote attackers to gain access and place arbitrary calls. |