CVE-2019-10162: A vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.10, 4.0.8 allowing an authorized user to cause the…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pdns (Alpine:v3.10) 4.1.10-r0; pdns (Alpine:v3.7) 4.0.8-r0; pdns (Debian:12) 4.1.6-3.
- Severity is disputed: the assigning authority (CNA) scores it 3.5, NVD 7.5.
Low priority for now. Upgrade to pdns (Alpine:v3.10) 4.1.10-r0; pdns (Alpine:v3.7) 4.0.8-r0; pdns (Debian:12) 4.1.6-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.10, 4.0.8 allowing an authorized user to cause the server to exit by inserting a crafted record in a MASTER type zone under their control. The issue is due to the fact that the Authoritative Server will exit when it runs into a parsing error while looking up the NS/A/AAAA records it is about to use for an outgoing notify.
- Published
- Jul 30, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 77th percentile
- CWE
- CWE-400
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.6%
CNA vs NVD score
- NVD
- 7.5
- CNA · redhat
- 3.5
- 4.0 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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| powerdns | authoritative | cpe:2.3:a:powerdns:authoritative |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
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.10, fixed in 4.0.8affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- 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.10
- powerdns authoritative4.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | pdns | before 4.1.10-r0 | 4.1.10-r0 |
| Alpine:v3.7 | pdns | before 4.0.8-r0 | 4.0.8-r0 |
| 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:Leap 15.0 | pdns | before 4.1.2-bp150.2.9.1 | 4.1.2-bp150.2.9.1 |
| 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 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)…55Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2018-10851Nov 29, 2018 · PowerDNS Authoritative Server 3.3.0 up to 4.1.4 excluding 4.1.5 and 4.0.6, and PowerDNS Recursor 3.2 up to 4.1.4 excluding 4.1.5 and 4.0.9…32Monitor
- ← EarlierCVE-2018-14626Nov 29, 2018 · PowerDNS Authoritative Server 4.1.0 up to 4.1.4 inclusive and PowerDNS Recursor 4.0.0 up to 4.1.4 inclusive are vulnerable to a packet…31Monitor
- Later →CVE-2019-10163Jul 30, 2019 · A Vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.9, 4.0.8 allowing a remote, authorized master server to…17Monitor
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 |
|---|---|---|
| alpine:pdns | 4.1.10-r0 · Alpine:v3.10 | Package registry (OSV) |
| 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.