Lucene search

K

5 matches found

CVE
CVE
added 2020/05/19 5:15 p.m.284 views

CVE-2020-10995

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 uses a crafted reply...

7.5CVSS7.3AI score0.00091EPSS
CVE
CVE
added 2020/05/19 4:15 p.m.271 views

CVE-2020-10030

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 gethostname() does n...

8.8CVSS9AI score0.00029EPSS
CVE
CVE
added 2020/10/16 6:15 a.m.235 views

CVE-2020-25829

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 query. This results ...

7.5CVSS7.1AI score0.00605EPSS
CVE
CVE
added 2020/07/01 6:15 p.m.209 views

CVE-2020-14196

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.

5.3CVSS5.4AI score0.0007EPSS
CVE
CVE
added 2020/05/19 2:15 p.m.200 views

CVE-2020-12244

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.

7.5CVSS7.4AI score0.0007EPSS