rpm package
suse/pdns-recursor&distro=SUSE Package Hub 12 SP1
pkg:rpm/suse/pdns-recursor&distro=SUSE%20Package%20Hub%2012%20SP1
Vulnerabilities (12)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-25829 | — | < 4.3.5-bp152.2.12.1 | 4.3.5-bp152.2.12.1 | Oct 16, 2020 | An issue has been found in PowerDNS Recursor before 4.1.18, 4.2.x before 4.2.5, and 4.3.x before 4.3.5. A remote attacker can cause the cached records for a given name to be updated to the Bogus DNSSEC validation state, instead of their actual DNSSEC Secure state, via a DNS ANY q | ||
| CVE-2020-14196 | — | < 4.1.12-bp151.4.6.1 | 4.1.12-bp151.4.6.1 | Jul 1, 2020 | In PowerDNS Recursor versions up to and including 4.3.1, 4.2.2 and 4.1.16, the ACL restricting access to the internal web server is not properly enforced. | ||
| CVE-2020-10995 | — | < 4.1.12-bp151.4.3.1 | 4.1.12-bp151.4.3.1 | May 19, 2020 | PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack u | ||
| CVE-2020-10030 | — | < 4.1.12-bp151.4.3.1 | 4.1.12-bp151.4.3.1 | May 19, 2020 | An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0. It allows an attacker (with enough privileges to change the system's hostname) to cause disclosure of uninitialized memory content via a stack-based out-of-bounds read. It only occurs on systems where g | ||
| CVE-2020-12244 | — | < 4.1.12-bp151.4.3.1 | 4.1.12-bp151.4.3.1 | May 19, 2020 | An issue has been found in PowerDNS Recursor 4.1.0 through 4.3.0 where records in the answer section of a NXDOMAIN response lacking an SOA were not properly validated in SyncRes::processAnswer, allowing an attacker to bypass DNSSEC validation. | ||
| CVE-2019-3807 | — | < 4.1.10-16.1 | 4.1.10-16.1 | Jan 29, 2019 | An 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 authoritative servers with the AA flag not set were not properly validated, allowing an attacker to bypass DNSSEC validation. | ||
| CVE-2019-3806 | — | < 4.1.10-16.1 | 4.1.10-16.1 | Jan 29, 2019 | An issue has been found in PowerDNS Recursor versions after 4.1.3 before 4.1.9 where Lua hooks are not properly applied to queries received over TCP in some specific combination of settings, possibly bypassing security policies enforced using Lua. | ||
| CVE-2018-16855 | — | < 4.1.8-13.1 | 4.1.8-13.1 | Dec 3, 2018 | An 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 memory read while computing the hash of the query for a packet cache lookup, possibly leading to a crash. | ||
| CVE-2018-14626 | — | < 4.1.8-13.1 | 4.1.8-13.1 | Nov 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 cache pollution via crafted query that can lead to denial of service. | ||
| CVE-2018-10851 | — | < 4.1.8-13.1 | 4.1.8-13.1 | Nov 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, are vulnerable to a memory leak while parsing malformed records that can lead to remote denial of service. | ||
| CVE-2018-14644 | — | < 4.1.8-13.1 | 4.1.8-13.1 | Nov 9, 2018 | An issue has been found in PowerDNS Recursor from 4.0.0 up to and including 4.1.4. A remote attacker sending a DNS query for a meta-type like OPT can lead to a zone being wrongly cached as failing DNSSEC validation. It only arises if the parent zone is signed, and all the authori | ||
| CVE-2018-1000003 | — | < 4.1.2-5.1 | 4.1.2-5.1 | Jan 22, 2018 | Improper input validation bugs in DNSSEC validators components in PowerDNS version 4.1.0 allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay. |
- CVE-2020-25829Oct 16, 2020affected < 4.3.5-bp152.2.12.1fixed 4.3.5-bp152.2.12.1
An issue has been found in PowerDNS Recursor before 4.1.18, 4.2.x before 4.2.5, and 4.3.x before 4.3.5. A remote attacker can cause the cached records for a given name to be updated to the Bogus DNSSEC validation state, instead of their actual DNSSEC Secure state, via a DNS ANY q
- CVE-2020-14196Jul 1, 2020affected < 4.1.12-bp151.4.6.1fixed 4.1.12-bp151.4.6.1
In PowerDNS Recursor versions up to and including 4.3.1, 4.2.2 and 4.1.16, the ACL restricting access to the internal web server is not properly enforced.
- CVE-2020-10995May 19, 2020affected < 4.1.12-bp151.4.3.1fixed 4.1.12-bp151.4.3.1
PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack u
- CVE-2020-10030May 19, 2020affected < 4.1.12-bp151.4.3.1fixed 4.1.12-bp151.4.3.1
An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0. It allows an attacker (with enough privileges to change the system's hostname) to cause disclosure of uninitialized memory content via a stack-based out-of-bounds read. It only occurs on systems where g
- CVE-2020-12244May 19, 2020affected < 4.1.12-bp151.4.3.1fixed 4.1.12-bp151.4.3.1
An issue has been found in PowerDNS Recursor 4.1.0 through 4.3.0 where records in the answer section of a NXDOMAIN response lacking an SOA were not properly validated in SyncRes::processAnswer, allowing an attacker to bypass DNSSEC validation.
- CVE-2019-3807Jan 29, 2019affected < 4.1.10-16.1fixed 4.1.10-16.1
An 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 authoritative servers with the AA flag not set were not properly validated, allowing an attacker to bypass DNSSEC validation.
- CVE-2019-3806Jan 29, 2019affected < 4.1.10-16.1fixed 4.1.10-16.1
An issue has been found in PowerDNS Recursor versions after 4.1.3 before 4.1.9 where Lua hooks are not properly applied to queries received over TCP in some specific combination of settings, possibly bypassing security policies enforced using Lua.
- CVE-2018-16855Dec 3, 2018affected < 4.1.8-13.1fixed 4.1.8-13.1
An 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 memory read while computing the hash of the query for a packet cache lookup, possibly leading to a crash.
- CVE-2018-14626Nov 29, 2018affected < 4.1.8-13.1fixed 4.1.8-13.1
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 cache pollution via crafted query that can lead to denial of service.
- CVE-2018-10851Nov 29, 2018affected < 4.1.8-13.1fixed 4.1.8-13.1
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, are vulnerable to a memory leak while parsing malformed records that can lead to remote denial of service.
- CVE-2018-14644Nov 9, 2018affected < 4.1.8-13.1fixed 4.1.8-13.1
An issue has been found in PowerDNS Recursor from 4.0.0 up to and including 4.1.4. A remote attacker sending a DNS query for a meta-type like OPT can lead to a zone being wrongly cached as failing DNSSEC validation. It only arises if the parent zone is signed, and all the authori
- CVE-2018-1000003Jan 22, 2018affected < 4.1.2-5.1fixed 4.1.2-5.1
Improper input validation bugs in DNSSEC validators components in PowerDNS version 4.1.0 allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay.