Dnsdist vulnerabilitiesRanked by how likely they are to be used.
Dnsdist is made by Powerdns. We track 3 published vulnerabilities in it, across 44 versions. None of them is on the list of flaws known to be exploited today. If you run Dnsdist, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Dnsdist vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Dnsdist's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Dnsdist 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.
- 4.6%CVE-2016-7069High
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.
- 2.6%CVE-2018-14663Medium
An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS...
- 0.8%CVE-2017-7557High
dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially allowing CSRF attack.
Running Dnsdist? 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
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.
- Matched to
- Dnsdist 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 3 published vulnerabilities listed under the name Dnsdist, across 44 versions.
None of Dnsdist's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Dnsdist. 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.