Authoritative Server vulnerabilitiesRanked by how likely they are to be used.
Authoritative Server is made by Powerdns. We track 7 published vulnerabilities in it, across 31 versions. None of them is on the list of flaws known to be exploited today. If you run Authoritative Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Authoritative Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Authoritative Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Authoritative Server 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.
- 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.
- 13%CVE-2019-3871High
A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7.
- 6.1%CVE-2008-3337Medium
PowerDNS Authoritative Server before 2.9.21.1 drops malformed queries, which might make it easier for remote attackers to poison DNS caches of other products running on other servers, a different issue than...
- 5.0%CVE-2022-27227High
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...
- 4.8%CVE-2012-0206Medium
common_startup.cc in PowerDNS (aka pdns) Authoritative Server before 2.9.22.5 and 3.x before 3.0.1 allows remote attackers to cause a denial of service (packet loop) via a crafted UDP DNS response.
- 3.8%CVE-2016-6172Medium
PowerDNS (aka pdns) Authoritative Server before 4.0.1 allows remote primary DNS servers to cause a denial of service (memory exhaustion and secondary DNS server crash) via a large (1) AXFR or (2) IXFR response.
Running Authoritative Server? 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
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.
- Matched to
- Authoritative Server 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.
We track 7 published vulnerabilities listed under the name Authoritative Server, across 31 versions.
None of Authoritative Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Authoritative Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.