A Vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.9, 4.0.8 allowing a remote, authorized master server to
A Vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.9, 4.0.8 allowing a remote, authorized master server to cause a high CPU load or even prevent any further updates to any slave zone by sending a large number of NOTIFY messages. Note that only servers configured as slaves are affected by this issue.
- Published
- Jul 30, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 61th percentile
- CWE
- CWE-770
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CNA vs NVD score
- NVD
- 4.3
- CNA · redhat
- 3.5
- 0.8 point gap
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| powerdns | authoritative | cpe:2.3:a:powerdns:authoritative |
| opensuse | backports | cpe:2.3:o:opensuse:backports |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse backportssle-15
- opensuse leap15.0
- opensuse leap15.1
- powerdns authoritative4.0.0 and later · before 4.0.8
- powerdns authoritative4.1.0 and later · before 4.1.9
- powerdns authoritative4.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
PowerDNS pdns
- fixed in 4.1.9, fixed in 4.0.8affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pdns | before 4.1.6-3 | 4.1.6-3 |
| Debian:8 | pdns | before 3.4.1-4+deb8u10 | 3.4.1-4+deb8u10 |
| Debian:9 | pdns | before 4.0.3-1+deb9u5 | 4.0.3-1+deb9u5 |
| openSUSE:Tumbleweed | pdns | before 4.5.1-1.5 | 4.5.1-1.5 |
| SUSE:Package Hub 12 SP1 | pdns | before 4.1.2-bp150.2.9.1 | 4.1.2-bp150.2.9.1 |
| SUSE:Package Hub 12 SP1 | pdns | before 4.1.2-bp150.2.9.1 | 4.1.2-bp150.2.9.1 |
| SUSE:Package Hub 15 SP1 | pdns | before 4.1.8-bp151.3.3.1 | 4.1.8-bp151.3.3.1 |
Same product
powerdns: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-1868The label decompression functionality in PowerDNS Recursor 3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2 and Authoritative (Auth) Server56Plan
- CVE-2016-5427PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a .49Plan
- CVE-2020-24698An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used.40Plan
- CVE-2015-5311PowerDNS (aka pdns) Authoritative Server 3.4.4 before 3.4.7 allows remote attackers to cause a denial of service (assertion failure and serv40Plan
- CVE-2026-33608Incomplete domain name sanitization during39Monitor
- CVE-2016-5426PowerDNS (aka pdns) Authoritative Server before 3.4.10 allows remote attackers to cause a denial of service (backend CPU consumption) via a 39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:pdns | 4.1.6-3 · Debian:12 | Package registry (OSV) |
| opensuse:pdns | 4.1.2-bp150.2.9.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:pdns | 4.1.2-bp150.2.9.1 · SUSE:Package Hub 12 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2019-08/msg00036.html
- lists.opensuse.org/opensuse-security-announce/2019-08/msg00054.html
- blog.powerdns.com/2019/06/21/powerdns-authoritative-server-4-0-8-and-4-1-10-released/
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10163
- doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2019-05.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.