Skip to content

Vendor

PowerDNS vulnerabilities

131 published CVES affecting PowerDNS, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
131
Critical
4
High
62
Medium
57
Low
8
Unscored
0
CISA KEV
0
Atom feed of PowerDNS alerts

Products

Latest PowerDNS CVEs

Newest publication first · page 1 of 6

  1. LowCVSS 3.7 EPSS 0.16%

    The issue is a DNSSEC validation bypass where wildcard expansion proofs (NSEC/NSEC3 records) are accepted without signature validation when the wildcard answer is a CNAME or DNAME record.

  2. LowCVSS 3.7 EPSS 0.22%

    An attacker can send a crafted EDNS OPT record that will be ignored by DNSdist’s filtering rules, but will be rewritten as a valid OPT record when EDNS Client Subnet is inserted, causing the backend to see the EDNS option(s) that DNSdist did not filter.

  3. MediumCVSS 5.3 EPSS 0.70%

    An attacker can send crafted DNS over HTTP/3 queries, triggering an exception that prevents some buffer from being freed right away. The buffer will be freed at the end of the QUIC connection, but on some setups it might be possible to open enough concurrent DoH3 streams to trigg...

  4. MediumCVSS 5.3 EPSS 0.70%

    An attacker might be able to cause outgoing TCP connections to backend to be stuck until a timeout occurs instead of being released immediately, by sending IXFR queries. This could be used to cause a denial of service if there is a limit to the number of concurrent connections to...

  5. LowCVSS 3.7 EPSS 0.22%

    An attacker sending a large number of crafted DNS queries might be able to trigger a dynamic block being inserted with a value causing invalid output to be produced in the prometheus endpoint. The prometheus endpoint will then be rejected by the scraper until the dynamic block ex...

  6. MediumCVSS 6.5 EPSS 0.24%

    Incomplete escaping of LDAP queries when running with 8bit-dns enabled allows users to perform queries of internal domain subtrees.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.