Overview 106 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 3 public PoC · 9 EPSS ≥ 0.5
106matches
0in Waratek scope0.0%
0protected0.0%
1exploited0.9%
0CISA KEV0.0%
3public PoC2.8%
9EPSS ≥ 0.58.5%
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
1
0.9%
Not applicable
105
99.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
106
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
0.9%
Working exploit published
0
0.0%
Proof of concept only
2
1.9%
Forecast only
6
5.7%
No public exploit
97
91.5%
split by
peak 38 / year
20054
Not applicable4
Medium3
Low1
not blocked4
No public exploit4
20063
Not applicable3
High1
Medium2
not blocked3
No public exploit3
20070
20084
Not applicable4
Medium4
not blocked4
No public exploit4
20090
20102
Not applicable2
High2
not blocked2
No public exploit2
20110
20122
Not applicable2
Medium2
not blocked2
No public exploit2
20130
20142
Not applicable2
Medium2
not blocked2
Forecast only1
No public exploit1
20153
Not applicable3
High2
Medium1
not blocked3
Forecast only2
No public exploit1
20163
Not applicable3
High2
Medium1
not blocked3
Forecast only1
No public exploit2
20171
Not applicable1
High1
not blocked1
No public exploit1
201819
Not applicable19
High10
Medium8
Low1
not blocked19
Forecast only2
No public exploit17
20196
Not applicable6
Critical1
High3
Medium2
not blocked6
No public exploit6
202010
Not applicable10
Critical1
High7
Medium2
not blocked10
No public exploit10
20211
Not applicable1
High1
not blocked1
Exploited1
20222
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20232
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20242
Outside Waratek scope1
Not applicable1
High2
not blocked2
Proof of concept only2
20252
Not applicable2
High1
Medium1
not blocked2
No public exploit2
202638
Not applicable38
Critical2
High20
Medium16
not blocked38
No public exploit38
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2006-4251 | High | 2006-11-14 | Not applicable | No public exploit | Buffer overflow in PowerDNS Recursor 3.1.3 and earlier might allow remote attackers to execute arbitrary code via a malformed TCP DNS query that prevents Recursor from properly calculating the TCP DNS query length. |
| CVE-2006-2069 | Medium | 2006-04-27 | Not applicable | No public exploit | The recursor in PowerDNS before 3.0.1 allows remote attackers to cause a denial of service (application crash) via malformed EDNS0 packets. |
| CVE-2005-0038 | Medium | 2005-12-31 | Not applicable | No public exploit | The DNS implementation of PowerDNS 2.9.16 and earlier allows remote attackers to cause a denial of service via a compressed DNS packet with a label length byte with an incorrect offset, which could trigger an infinite loop. |
| CVE-2005-2302 | Low | 2005-07-19 | Not applicable | No public exploit | PowerDNS before 2.9.18, when allowing recursion to a restricted range of IP addresses, does not properly handle questions from clients that are denied recursion, which could cause a "blank out" of answers to those clients that are allowed to use recursion. |
| CVE-2005-2301 | Medium | 2005-07-19 | Not applicable | No public exploit | PowerDNS before 2.9.18, when running with an LDAP backend, does not properly escape LDAP queries, which allows remote attackers to cause a denial of service (failure to answer ldap questions) and possibly conduct an LDAP injection attack. |
| CVE-2005-0428 | Medium | 2005-05-02 | Not applicable | No public exploit | The DNSPacket::expand method in dnspacket.cc in PowerDNS before 2.9.17 allows remote attackers to cause a denial of service by sending a random stream of bytes. |