Transfer requests received over DoH can lead to a denial of service in DNSdist
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PowerDNS | DNSdist | unaffected |
|
No data.
No data.
No data available yet.
Vendor Workaround
Option 1: refuse incoming XFR requests via a DNSdist rule: addAction(OrRule({QTypeRule(DNSQType.AXFR), QTypeRule(DNSQType.IXFR)}), RCodeAction(DNSRCode.REFUSED)). Option 2: switch to the legacy h2o provider by setting library='h2o' in the addDOHLocal directive
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-22909 | When incoming DNS over HTTPS support is enabled using the nghttp2 provider, and queries are routed to a tcp-only or DNS over TLS backend, an attacker can trigger an assertion failure in DNSdist by sending a request for a zone transfer (AXFR or IXFR) over DNS over HTTPS, causing the process to stop and thus leading to a Denial of Service. DNS over HTTPS is not enabled by default, and backends are using plain DNS (Do53) by default. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.078% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Powerdns
Powerdns dnsdist |
|
| CPEs | cpe:2.3:a:powerdns:dnsdist:1.9.0:*:*:*:*:*:*:* cpe:2.3:a:powerdns:dnsdist:1.9.1:*:*:*:*:*:*:* cpe:2.3:a:powerdns:dnsdist:1.9.2:*:*:*:*:*:*:* cpe:2.3:a:powerdns:dnsdist:1.9.3:*:*:*:*:*:*:* |
|
| Vendors & Products |
Powerdns
Powerdns dnsdist |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When incoming DNS over HTTPS support is enabled using the nghttp2 provider, and queries are routed to a tcp-only or DNS over TLS backend, an attacker can trigger an assertion failure in DNSdist by sending a request for a zone transfer (AXFR or IXFR) over DNS over HTTPS, causing the process to stop and thus leading to a Denial of Service. DNS over HTTPS is not enabled by default, and backends are using plain DNS (Do53) by default. | When incoming DNS over HTTPS support is enabled using the nghttp2 provider, and queries are routed to a tcp-only or DNS over TLS backend, an attacker can trigger an assertion failure in DNSdist by sending a request for a zone transfer (AXFR or IXFR) over DNS over HTTPS, causing the process to stop and thus leading to a Denial of Service. DNS over HTTPS is not enabled by default, and backends are using plain DNS (Do53) by default. |