Vulnerabilities

RRSIGs with too few labels can lead to bypass of DNSSEC wildcard validation

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.

If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data.

This fix provides extra hardening for the 5.4.x branch by doing extra validation of incoming answers from authoritative servers.

Spoofing replies to Recursor might mark an IP of an authoritative server as not supporting EDNS, causing valdiation of DNSSEC records served by that server to fail.

An invalid zone might pass ZONEMD validation while it should not.

Incomplete validation of the SOA record present in a catalog zone might lead to a crash.

A malicious authoritative server can send a crafted zone via the ZoneToCache function that leads to a crash of the Recursor due to insuffcient input validation.

ECS zero scoped answers are stored in the packet cache while they should not.

A malicious authoritative server can send a crafted zone via the ZoneToCache function that leads to cache poisoning.

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 optio…

An attacker can send crafted DNS over HTTP/3 queries, triggering an exception that prevents some buffer from being freed right away.

An out-of-bounds read might happen when SetMacAddrAction is used, potentially resulting in uninitialized memory being sent over the network or a crash.

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.

An attacker might be able to delay the processing of DoH3 queries by sending DoH3 GET queries with an invalid DATA frame.

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.

An attacker can send a web request that causes unlimited memory allocation in the internal web server, leading to a denial of service.

Incorrect Behaviour of Views with TCP PROXY Requests

Concurrency and locking defects in GSS-TSIG

Insufficient Validation of Autoprimary SOA Queries

Insufficient Validation of Names During AXFR

Insufficient Validation of Member Zone Data May Cause Catalog Zone Transfer to Fail

An operator allowed to use the REST API can cause the Authoritative server to produce invalid HTTPS or SVCB record data, which can in turn cause LMDB database corruption, if using the LMDB backend.

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.

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