CVE-2018-10851
https://notcve.org/view.php?id=CVE-2018-10851
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. PowerDNS Authoritative Server desde la versión 3.3.0 hasta la 4.1.4 excluyendo las versiones 4.1.5 y 4.0.6, y PowerDNS Recursor desde la versión 3.2 hasta la 4.1.4 excluyendo las versiones 4.1.5 y 4.0.9, son vulnerables a una fuga de memoria cuando se analizan registros mal formados que pueden conducir a una denegación de servicio (DoS) remota. • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10851 https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2018-03.html https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-04.html • CWE-400: Uncontrolled Resource Consumption CWE-772: Missing Release of Resource after Effective Lifetime •
CVE-2018-14626
https://notcve.org/view.php?id=CVE-2018-14626
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. PowerDNS Authoritative Server desde la versión 4.1.0 hasta la 4.1.4 y PowerDNS Recursor desde la versión 4.0.0 hasta la 4.1.4, son vulnerables a una contaminación de memora caché de paquetes mediante una consulta manipulada que puede provocar una denegación de servicio (DoS). • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14626 https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2018-05.html https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-06.html • CWE-400: Uncontrolled Resource Consumption •
CVE-2018-14663
https://notcve.org/view.php?id=CVE-2018-14663
An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the 'useClientSubnet' or the experimental 'addXPF' parameters are used when declaring a new backend. Se ha encontrado un problema en PowerDNS DNSDist en versiones anteriores a la 1.3.3, permitiendo a un atacante remoto manipular una consulta DNS con datos finales. Esto permite que la adición de un registro por parte de dnssist, por ejemplo, un registro OPT cuando se añade el EDNS Client Subnet, podría resultar en el contrabando de datos finales al backend como si dicho registro fuera válido cuando dnsdist no lo detecte. • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14663 https://dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2018-08.html • CWE-20: Improper Input Validation •
CVE-2018-14644
https://notcve.org/view.php?id=CVE-2018-14644
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 authoritative servers for that parent zone answer with FORMERR to a query for at least one of the meta-types. As a result, subsequent queries from clients requesting DNSSEC validation will be answered with a ServFail. Se ha encontrado un problema en PowerDNS Recursor desde la versión 4.0.0 hasta la versión 4.1.4 inclusive. • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14644 https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-07.html • CWE-20: Improper Input Validation •
CVE-2016-7069
https://notcve.org/view.php?id=CVE-2016-7069
An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing responses from a backend. When dnsdist is configured to add EDNS Client Subnet to a query, the response may contain an EDNS0 OPT record that has to be removed before forwarding the response to the initial client. On a 32-bit system, the pointer arithmetic used when parsing the received response to remove that record might trigger an undefined behavior leading to a crash. Se ha descubierto un problema en dnsdist en versiones anteriores a la 1.2.0 en la forma en la que se gestionan los registros EDNS0 OPT al analizar respuestas desde un backend. Cuando dnsdist está configurado para añadir EDNS Client Subnet a una consulta, la respuesta podría contener un registro EDNS0 OPT que debe ser eliminado antes de reenviar la respuesta al cliente inicial. • http://www.securityfocus.com/bid/100509 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-7069 https://dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2017-01.html • CWE-20: Improper Input Validation •