Overview 54 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 3 public PoC · 7 EPSS ≥ 0.5
54matches
0in Waratek scope0.0%
0protected0.0%
1exploited1.9%
0CISA KEV0.0%
3public PoC5.6%
7EPSS ≥ 0.513.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
1
1.9%
Not applicable
53
98.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
54
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
1.9%
Working exploit published
0
0.0%
Proof of concept only
2
3.7%
Forecast only
4
7.4%
No public exploit
47
87.0%
split by
peak 20 / year
20061
Not applicable1
High1
not blocked1
No public exploit1
20070
20080
20090
20102
Not applicable2
High2
not blocked2
No public exploit2
20110
20120
20130
20140
20152
Not applicable2
High2
not blocked2
Forecast only1
No public exploit1
20162
Not applicable2
High2
not blocked2
Forecast only1
No public exploit1
20171
Not applicable1
High1
not blocked1
No public exploit1
201810
Not applicable10
High10
not blocked10
Forecast only2
No public exploit8
20193
Not applicable3
High3
not blocked3
No public exploit3
20207
Not applicable7
High7
not blocked7
No public exploit7
20211
Not applicable1
High1
not blocked1
Exploited1
20221
Not applicable1
High1
not blocked1
No public exploit1
20231
Not applicable1
High1
not blocked1
No public exploit1
20242
Outside Waratek scope1
Not applicable1
High2
not blocked2
Proof of concept only2
20251
Not applicable1
High1
not blocked1
No public exploit1
202620
Not applicable20
High20
not blocked20
No public exploit20
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-42002 | High | 2026-05-21 | Not applicable | No public exploit | Concurrency and locking defects in GSS-TSIG |
| CVE-2026-42001 | High | 2026-05-21 | Not applicable | No public exploit | Insufficient Validation of Autoprimary SOA Queries |
| CVE-2026-42000 | High | 2026-05-21 | Not applicable | No public exploit | Insufficient Validation of Names During AXFR |
| CVE-2026-33610 | High | 2026-04-22 | Not applicable | No public exploit | A rogue primary server may cause file descriptor exhaustion and eventually a denial of service, when a PowerDNS secondary server forwards a DNS update request to it. |
| CVE-2026-33602 | High | 2026-04-22 | Not applicable | No public exploit | A rogue backend can send a crafted UDP response with a query ID off by one related to the maximum configured value, triggering an out-of-bounds write leading to a denial of service. |
| CVE-2026-33599 | High | 2026-04-22 | Not applicable | No public exploit | A rogue backend can send a crafted SVCB response to a Discovery of Designated Resolvers request, when requested via either the autoUpgrade (Lua) option to newServer or auto_upgrade (YAML) settings. DDR upgrade is not enabled by default. |
| CVE-2026-33597 | High | 2026-04-22 | Not applicable | No public exploit | PRSD detection denial of service |
| CVE-2026-33595 | High | 2026-04-22 | Not applicable | No public exploit | A client can trigger excessive memory allocation by generating a lot of errors responses over a single DoQ and DoH3 connection, as some resources were not properly released until the end of the connection. |
| CVE-2026-33594 | High | 2026-04-22 | Not applicable | No public exploit | A client can trigger excessive memory allocation by generating a lot of queries that are routed to an overloaded DoH backend, causing queries to accumulate into a buffer that will not be released until the end of the connection. |
| CVE-2026-33593 | High | 2026-04-22 | Not applicable | No public exploit | A client can trigger a divide by zero error leading to crash by sending a crafted DNSCrypt query. |
| CVE-2026-33260 | High | 2026-04-22 | Not applicable | No public exploit | An attacker can send a web request that causes unlimited memory allocation in the internal web server, leading to a denial of service. The internal web server is disabled by default. |
| CVE-2026-33258 | High | 2026-04-22 | Not applicable | No public exploit | By publishing and querying a crafted zone an attacker can cause allocation of large entries in the negative and aggressive NSEC(3) caches. |
| CVE-2026-33257 | High | 2026-04-22 | Not applicable | No public exploit | An attacker can send a web request that causes unlimited memory allocation in the internal web server, leading to a denial of service. The internal web server is disabled by default. |
| CVE-2026-33256 | High | 2026-04-22 | Not applicable | No public exploit | An attacker can send a web request that causes unlimited memory allocation in the internal web server, leading to a denial of service. The internal web server is disabled by default. |
| CVE-2026-33254 | High | 2026-04-22 | Not applicable | No public exploit | An attacker can create a large number of concurrent DoQ or DoH3 connections, causing unlimited memory allocation in DNSdist and leading to a denial of service. DOQ and DoH3 are disabled by default. |
| CVE-2026-27854 | High | 2026-03-31 | Not applicable | No public exploit | An attacker might be able to trigger a use-after-free by sending crafted DNS queries to a DNSdist using the DNSQuestion:getEDNSOptions method in custom Lua code. In some cases DNSQuestion:getEDNSOptions might refer to a version of the DNS packet that has been modified, thus triggering a use-after-free and potentially a crash resulting in denial of service. |
| CVE-2026-27853 | High | 2026-03-31 | Not applicable | No public exploit | An attacker might be able to trigger an out-of-bounds write by sending crafted DNS responses to a DNSdist using the DNSQuestion:changeName or DNSResponse:changeName methods in custom Lua code. In some cases the rewritten packet might become larger than the initial response and even exceed 65535 bytes, potentially leading to a crash resulting in denial of service. |
| CVE-2026-24030 | High | 2026-03-31 | Not applicable | No public exploit | An attacker might be able to trick DNSdist into allocating too much memory while processing DNS over QUIC or DNS over HTTP/3 payloads, resulting in a denial of service. In setups with a large quantity of memory available this usually results in an exception and the QUIC connection is properly closed, but in some cases the system might enter an out-of-memory state instead and terminate the process. |
| CVE-2026-24028 | High | 2026-03-31 | Not applicable | No public exploit | An attacker might be able to trigger an out-of-bounds read by sending a crafted DNS response packet, when custom Lua code uses newDNSPacketOverlay to parse DNS packets. The out-of-bounds read might trigger a crash, leading to a denial of service, or access unrelated memory, leading to potential information disclosure. |
| CVE-2025-59023 | High | 2026-02-09 | Not applicable | No public exploit | Crafted delegations or IP fragments can poison cached delegations in Recursor. |
| CVE-2025-59030 | High | 2025-12-09 | Not applicable | No public exploit | An attacker can trigger the removal of cached records by sending a NOTIFY query over TCP. |
| CVE-2023-50868 | High | 2024-02-14 | Outside Waratek scope | Proof of concept only | The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations. |
| CVE-2023-50387 | High | 2024-02-14 | Not applicable | Proof of concept only | Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records. |
| CVE-2023-22617 | High | 2023-01-21 | Not applicable | No public exploit | A remote attacker might be able to cause infinite recursion in PowerDNS Recursor 4.8.0 via a DNS query that retrieves DS records for a misconfigured domain, because QName minimization is used in QM fallback mode. This is fixed in 4.8.1. |
| CVE-2022-27227 | High | 2022-03-25 | Not applicable | No public exploit | In PowerDNS Authoritative Server before 4.4.3, 4.5.x before 4.5.4, and 4.6.x before 4.6.1 and PowerDNS Recursor before 4.4.8, 4.5.x before 4.5.8, and 4.6.x before 4.6.1, insufficient validation of an IXFR end condition causes incomplete zone transfers to be handled as successful transfers. |
| CVE-2021-36754 | High | 2021-07-30 | Not applicable | Exploited | PowerDNS Authoritative Server 4.5.0 before 4.5.1 allows anybody to crash the process by sending a specific query (QTYPE 65535) that causes an out-of-bounds exception. |
| CVE-2020-25829 | High | 2020-10-16 | Not applicable | No public exploit | An issue has been found in PowerDNS Recursor before 4.1.18, 4.2.x before 4.2.5, and 4.3.x before 4.3.5. A remote attacker can cause the cached records for a given name to be updated to the Bogus DNSSEC validation state, instead of their actual DNSSEC Secure state, via a DNS ANY query. This results in a denial of service for installation that always validate (dnssec=validate), and for clients requesting validation when on-demand validation is enabled (dnssec=process). |
| CVE-2020-24697 | High | 2020-10-02 | Not applicable | No public exploit | An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used. A remote, unauthenticated attacker can cause a denial of service by sending crafted queries with a GSS-TSIG signature. |
| CVE-2020-24696 | High | 2020-10-02 | Not applicable | No public exploit | An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used. A remote, unauthenticated attacker can trigger a race condition leading to a crash, or possibly arbitrary code execution, by sending crafted queries with a GSS-TSIG signature. |
| CVE-2020-12244 | High | 2020-05-19 | Not applicable | No public exploit | An issue has been found in PowerDNS Recursor 4.1.0 through 4.3.0 where records in the answer section of a NXDOMAIN response lacking an SOA were not properly validated in SyncRes::processAnswer, allowing an attacker to bypass DNSSEC validation. |
| CVE-2020-10995 | High | 2020-05-19 | Not applicable | No public exploit | PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue. |
| CVE-2020-10030 | High | 2020-05-19 | Not applicable | No public exploit | An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0. It allows an attacker (with enough privileges to change the system's hostname) to cause disclosure of uninitialized memory content via a stack-based out-of-bounds read. It only occurs on systems where gethostname() does not have '\0' termination of the returned string if the hostname is larger than the supplied buffer. (Linux systems are not affected because the buffer is always large enough. OpenBSD systems are not affected because the returned hostname always has '\0' termination.) Under some conditions, this issue can lead to the writing of one '\0' byte out-of-bounds on the stack, causing a denial of service or possibly arbitrary code execution. |
| CVE-2015-5230 | High | 2020-01-15 | Not applicable | No public exploit | The DNS packet parsing/generation code in PowerDNS (aka pdns) Authoritative Server 3.4.x before 3.4.6 allows remote attackers to cause a denial of service (crash) via crafted query packets. |
| CVE-2019-10162 | High | 2019-07-30 | Not applicable | No public exploit | A vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.10, 4.0.8 allowing an authorized user to cause the server to exit by inserting a crafted record in a MASTER type zone under their control. The issue is due to the fact that the Authoritative Server will exit when it runs into a parsing error while looking up the NS/A/AAAA records it is about to use for an outgoing notify. |
| CVE-2019-3871 | High | 2019-03-21 | Not applicable | No public exploit | A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7. An insufficient validation of data coming from the user when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend, allowing a remote user to cause a denial of service by making the server connect to an invalid endpoint, or possibly information disclosure by making the server connect to an internal endpoint and somehow extracting meaningful information about the response |
| CVE-2019-3806 | High | 2019-01-29 | Not applicable | No public exploit | An issue has been found in PowerDNS Recursor versions after 4.1.3 before 4.1.9 where Lua hooks are not properly applied to queries received over TCP in some specific combination of settings, possibly bypassing security policies enforced using Lua. |
| CVE-2018-16855 | High | 2018-12-03 | Not applicable | Forecast only | An issue has been found in PowerDNS Recursor before version 4.1.8 where a remote attacker sending a DNS query can trigger an out-of-bounds memory read while computing the hash of the query for a packet cache lookup, possibly leading to a crash. |
| CVE-2018-14626 | High | 2018-11-29 | Not applicable | No public exploit | PowerDNS Authoritative Server 4.1.0 up to 4.1.4 inclusive and PowerDNS Recursor 4.0.0 up to 4.1.4 inclusive are vulnerable to a packet cache pollution via crafted query that can lead to denial of service. |
| CVE-2018-10851 | High | 2018-11-29 | Not applicable | No public exploit | PowerDNS Authoritative Server 3.3.0 up to 4.1.4 excluding 4.1.5 and 4.0.6, and PowerDNS Recursor 3.2 up to 4.1.4 excluding 4.1.5 and 4.0.9, are vulnerable to a memory leak while parsing malformed records that can lead to remote denial of service. |
| CVE-2016-2120 | High | 2018-11-01 | Not applicable | No public exploit | An issue has been found in PowerDNS Authoritative Server versions up to and including 3.4.10, 4.0.1 allowing an authorized user to crash the server by inserting a specially crafted record in a zone under their control then sending a DNS query for that record. The issue is due to an integer overflow when checking if the content of the record matches the expected size, allowing an attacker to cause a read past the buffer boundary. |
| CVE-2016-7069 | High | 2018-09-11 | Not applicable | No public exploit | An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing responses from a backend. When dnsdist is configured to add EDNS Client Subnet to a query, the response may contain an EDNS0 OPT record that has to be removed before forwarding the response to the initial client. On a 32-bit system, the pointer arithmetic used when parsing the received response to remove that record might trigger an undefined behavior leading to a crash. |
| CVE-2016-7068 | High | 2018-09-11 | Not applicable | No public exploit | An issue has been found in PowerDNS before 3.4.11 and 4.0.2, and PowerDNS recursor before 3.7.4 and 4.0.4, allowing a remote, unauthenticated attacker to cause an abnormal CPU usage load on the PowerDNS server by sending crafted DNS queries, which might result in a partial denial of service if the system becomes overloaded. This issue is based on the fact that the PowerDNS server parses all records present in a query regardless of whether they are needed or even legitimate. A specially crafted query containing a large number of records can be used to take advantage of that behaviour. |
| CVE-2016-7072 | High | 2018-09-10 | Not applicable | No public exploit | An issue has been found in PowerDNS Authoritative Server before 3.4.11 and 4.0.2 allowing a remote, unauthenticated attacker to cause a denial of service by opening a large number of TCP connections to the web server. If the web server runs out of file descriptors, it triggers an exception and terminates the whole PowerDNS process. While it's more complicated for an unauthorized attacker to make the web server run out of file descriptors since its connection will be closed just after being accepted, it might still be possible. |
| CVE-2017-15120 | High | 2018-07-27 | Not applicable | Forecast only | An issue has been found in the parsing of authoritative answers in PowerDNS Recursor before 4.0.8, leading to a NULL pointer dereference when parsing a specially crafted answer containing a CNAME of a different class than IN. An unauthenticated remote attacker could cause a denial of service. |
| CVE-2018-1046 | High | 2018-07-16 | Not applicable | No public exploit | pdns before version 4.1.2 is vulnerable to a buffer overflow in dnsreplay. In the dnsreplay tool provided with PowerDNS Authoritative, replaying a specially crafted PCAP file can trigger a stack-based buffer overflow, leading to a crash and potentially arbitrary code execution. This buffer overflow only occurs when the -ecs-stamp option of dnsreplay is used. |
| CVE-2017-15091 | High | 2018-01-23 | Not applicable | No public exploit | An issue has been found in the API component of PowerDNS Authoritative 4.x up to and including 4.0.4 and 3.x up to and including 3.4.11, where some operations that have an impact on the state of the server are still allowed even though the API has been configured as read-only via the api-readonly keyword. This missing check allows an attacker with valid API credentials to flush the cache, trigger a zone transfer or send a NOTIFY. |
| CVE-2017-7557 | High | 2017-08-22 | Not applicable | No public exploit | dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially allowing CSRF attack. |
| CVE-2016-5427 | High | 2016-09-21 | Not applicable | Forecast only | PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a . (dot) inside labels, which allows remote attackers to cause a denial of service (backend CPU consumption) via a crafted DNS query. |
| CVE-2016-5426 | High | 2016-09-21 | Not applicable | No public exploit | PowerDNS (aka pdns) Authoritative Server before 3.4.10 allows remote attackers to cause a denial of service (backend CPU consumption) via a long qname. |
| CVE-2015-5470 | High | 2015-11-02 | Not applicable | No public exploit | The label decompression functionality in PowerDNS Recursor before 3.6.4 and 3.7.x before 3.7.3 and Authoritative (Auth) Server before 3.3.3 and 3.4.x before 3.4.5 allows remote attackers to cause a denial of service (CPU consumption or crash) via a request with a long name that refers to itself. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-1868. |
| CVE-2015-1868 | High | 2015-05-18 | Not applicable | Forecast only | The label decompression functionality in PowerDNS Recursor 3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2 and Authoritative (Auth) Server 3.2.x, 3.3.x before 3.3.2, and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service (CPU consumption or crash) via a request with a name that refers to itself. |
| CVE-2009-4010 | High | 2010-01-08 | Not applicable | No public exploit | Unspecified vulnerability in PowerDNS Recursor before 3.1.7.2 allows remote attackers to spoof DNS data via crafted zones. |
| CVE-2009-4009 | High | 2010-01-08 | Not applicable | No public exploit | Buffer overflow in PowerDNS Recursor before 3.1.7.2 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via crafted packets. |
| 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. |