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.
Metrics
Affected Vendors & Products
References
History
Thu, 13 Feb 2025 18:15:00 +0000
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
|
Thu, 13 Feb 2025 17:45:00 +0000
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. |

Status: PUBLISHED
Assigner: OX
Published:
Updated: 2025-02-13T17:40:49.395Z
Reserved: 2024-02-08T08:15:37.204Z
Link: CVE-2024-25581

Updated: 2024-08-01T23:44:09.662Z

Status : Awaiting Analysis
Published: 2024-05-14T15:05:29.707
Modified: 2025-02-13T18:17:14.117
Link: CVE-2024-25581

No data.