Powerdns vulnerabilitiesNone on the known-exploited list.
Powerdns has 65 published vulnerabilities across 7 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Recursor, with 34. If you run Powerdns software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Powerdns products have the most vulnerabilities?
Recursor leads with 34 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Powerdns vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Powerdns's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Powerdns flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2023-50387High
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.
- 82%CVE-2015-1868High
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...
- 69%CVE-2014-8601Medium
PowerDNS Recursor before 3.6.2 does not limit delegation chaining, which allows remote attackers to cause a denial of service ("performance degradations") via a large or infinite number of referrals, as demonstrated...
- 67%CVE-2015-5311Medium
PowerDNS (aka pdns) Authoritative Server 3.4.4 before 3.4.7 allows remote attackers to cause a denial of service (assertion failure and server crash) via crafted query packets.
- 65%CVE-2021-36754High
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.
- 63%CVE-2016-5427High
PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a .
- 59%CVE-2018-16855High
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,...
- 51%CVE-2017-15120High
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...
- 31%CVE-2016-5426High
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.
- 24%CVE-2020-10030High
An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0.
All Powerdns products we track.
7 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
- Recursorrecursor34 vulnerabilities170 versions
- Authoritativeauthoritative20 vulnerabilities91 versions
- Authoritative Serverauthoritative_server7 vulnerabilities31 versions
- Powerdnspowerdns7 vulnerabilities41 versions
- Dnsdistdnsdist3 vulnerabilities44 versions
- Powerdns Recursorpowerdns_recursor2 vulnerabilities2 versions
- Pdnspdns1 vulnerability12 versions
Running Powerdns? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Powerdns on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 65 published vulnerabilities across 7 products and 391 versions from Powerdns.
None of Powerdns's vulnerabilities is on the list of flaws known to be exploited today.
Recursor, with 34 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Powerdns products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.