PowerDNS Recursor before 3.1.6 does not always use the strongest random number generator for source port selection, which makes it easier fo
PowerDNS Recursor before 3.1.6 does not always use the strongest random number generator for source port selection, which makes it easier for remote attack vectors to conduct DNS cache poisoning. NOTE: this is related to incomplete integration of security improvements associated with addressing CVE-2008-1637.
- Published
- Jul 18, 2008
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-189
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| powerdns | recursor | cpe:2.3:a:powerdns:recursor |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- powerdns recursorup to 3.1.5 inclusive
- powerdns recursor3.0
- powerdns recursor3.0.1
- powerdns recursor3.1.1
- powerdns recursor3.1.2
- powerdns recursor3.1.3
- powerdns recursor3.1.4
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-recursor | before 3.1.7-1 | 3.1.7-1 |
| Debian:4.0 | pdns-recursor | before 3.1.4-1+etch2 | 3.1.4-1+etch2 |
Same product
powerdns: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-16855An issue has been found in PowerDNS Recursor before version 4.1.8 where a remote attacker sending a DNS query can trigger an out-of-bounds m48Plan
- CVE-2017-15120An issue has been found in the parsing of authoritative answers in PowerDNS Recursor before 4.0.8, leading to a NULL pointer dereference whe45Plan
- CVE-2009-4009Buffer overflow in PowerDNS Recursor before 3.1.7.2 allows remote attackers to cause a denial of service (daemon crash) or possibly execute 45Plan
- CVE-2020-10030An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0.42Plan
- CVE-2014-8601PowerDNS Recursor before 3.6.2 does not limit delegation chaining, which allows remote attackers to cause a denial of service ("performance 41Plan
- CVE-2019-3807An issue has been found in PowerDNS Recursor versions 4.1.x before 4.1.9 where records in the answer section of responses received from auth39Monitor
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-recursor | 3.1.7-1 · Debian:12 | 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.
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
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- doc.powerdns.com/changelog.html#CHANGELOG-RECURSOR-3-1-6
- secunia.com/advisories/31311
- wiki.powerdns.com/cgi-bin/trac.fcgi/changeset/1179
- www.openwall.com/lists/oss-security/2008/07/09/10
- www.openwall.com/lists/oss-security/2008/07/10/6
- www.openwall.com/lists/oss-security/2008/07/16/12
- www.securityfocus.com/bid/30782
- exchange.xforce.ibmcloud.com/vulnerabilities/43925
- www.redhat.com/archives/fedora-package-announce/2008-July/msg01353.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.