Skip to main content
No exploitation reportedFix available

CVE-2024-25581

No exploitation reported by the sources we read.

  • Published2024-05-14
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-05-1415:05CVE publishedNVD

Versions per branch

CISA-ADP
Powerdns dnsdist
BranchAffectedFixed in
1.9= 1.9.0no fix published
1.9= 1.9.1no fix published
1.9= 1.9.2no fix published
1.9= 1.9.3no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As OX, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • PowerDNS DNSdistother versions: not affected

    package dnsdisthttps://repo.powerdns.com/

    Affected
    • = 1.9.0no fix stated
    • = 1.9.1no fix stated
    • = 1.9.2no fix stated
    • = 1.9.3no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-06-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • dnsdistopenSUSE:Tumbleweedall versions · fixed in 1.9.4-1.1
  • dnsdistDebian:14all versions · fixed in 1.9.4-1
  • dnsdistDebian:13all versions · fixed in 1.9.4-1
  • dnsdistCleanStartall versions · fixed in 1.9.4-r0
  • dnsdistAlpine:v3.24all versions · fixed in 1.9.4-r0
  • dnsdistAlpine:v3.23all versions · fixed in 1.9.4-r0
  • dnsdistAlpine:v3.22all versions · fixed in 1.9.4-r0
  • dnsdistAlpine:v3.21all versions · fixed in 1.9.4-r0

1 more package range on OSV.dev

Vendor advisories

  • CVE-2024-25581 Red Hat Product Security

    dnsdist: Transfer requests received over DoH can lead to a denial of service in DNSdist

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-05-14
Last Modified
2026-06-17
NVD status
Deferred
GitHub Advisory
GHSA-55g9-rgmx-hvww

Frequently asked questions

What is CVE-2024-25581?

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.

Is CVE-2024-25581 actively exploited?

Active exploitation of CVE-2024-25581 has not been confirmed. Its EPSS score was 1.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-25581?

CVE-2024-25581 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running dnsdist? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record