PowerDNS Authoritative 3.4.11

CPE Details

PowerDNS Authoritative 3.4.11
powerdns
authoritative
3.4.11
2018-09-17
13h32 +00:00
2018-09-17
13h32 +00:00
CPE NVD
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:powerdns:authoritative:3.4.11:*:*:*:*:*:*:*

Informations

Vendor

powerdns

Product

authoritative

Version

3.4.11

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2020-24698 2020-10-02 06h23 +00:00 An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used. A remote, unauthenticated attacker might be able to cause a double-free, leading to a crash or possibly arbitrary code execution. by sending crafted queries with a GSS-TSIG signature.
9.8
Critique
CVE-2020-24697 2020-10-02 06h23 +00:00 An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used. A remote, unauthenticated attacker can cause a denial of service by sending crafted queries with a GSS-TSIG signature.
7.5
Haute
CVE-2020-24696 2020-10-02 06h21 +00:00 An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used. A remote, unauthenticated attacker can trigger a race condition leading to a crash, or possibly arbitrary code execution, by sending crafted queries with a GSS-TSIG signature.
8.1
Haute
CVE-2020-17482 2020-10-02 06h21 +00:00 An issue has been found in PowerDNS Authoritative Server before 4.3.1 where an authorized user with the ability to insert crafted records into a zone might be able to leak the content of uninitialized memory.
4.3
Moyen
CVE-2018-10851 2018-11-29 17h00 +00:00 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.
7.5
Haute
CVE-2017-15091 2018-01-23 15h00 +00:00 An issue has been found in the API component of PowerDNS Authoritative 4.x up to and including 4.0.4 and 3.x up to and including 3.4.11, where some operations that have an impact on the state of the server are still allowed even though the API has been configured as read-only via the api-readonly keyword. This missing check allows an attacker with valid API credentials to flush the cache, trigger a zone transfer or send a NOTIFY.
7.1
Haute