Filtered by vendor Powerdns
Subscribe
Total
64 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2014-3614 | 1 Powerdns | 1 Powerdns Recursor | 2024-11-21 | 5.0 MEDIUM | N/A |
Unspecified vulnerability in PowerDNS Recursor (aka pdns_recursor) 3.6.x before 3.6.1 allows remote attackers to cause a denial of service (crash) via an unknown sequence of malformed packets. | |||||
CVE-2012-1193 | 1 Powerdns | 1 Powerdns Recursor | 2024-11-21 | 6.4 MEDIUM | N/A |
The resolver in PowerDNS Recursor (aka pdns_recursor) 3.3 overwrites cached server names and TTL values in NS records during the processing of a response to an A record query, which allows remote attackers to trigger continued resolvability of revoked domain names via a "ghost domain names" attack. | |||||
CVE-2012-0206 | 1 Powerdns | 1 Authoritative Server | 2024-11-21 | 5.0 MEDIUM | N/A |
common_startup.cc in PowerDNS (aka pdns) Authoritative Server before 2.9.22.5 and 3.x before 3.0.1 allows remote attackers to cause a denial of service (packet loop) via a crafted UDP DNS response. | |||||
CVE-2009-4010 | 1 Powerdns | 1 Recursor | 2024-11-21 | 7.5 HIGH | N/A |
Unspecified vulnerability in PowerDNS Recursor before 3.1.7.2 allows remote attackers to spoof DNS data via crafted zones. | |||||
CVE-2009-4009 | 1 Powerdns | 1 Recursor | 2024-11-21 | 10.0 HIGH | N/A |
Buffer overflow in PowerDNS Recursor before 3.1.7.2 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via crafted packets. | |||||
CVE-2008-5277 | 1 Powerdns | 1 Powerdns | 2024-11-21 | 4.3 MEDIUM | N/A |
PowerDNS before 2.9.21.2 allows remote attackers to cause a denial of service (daemon crash) via a CH HINFO query. | |||||
CVE-2008-3337 | 1 Powerdns | 2 Authoritative Server, Powerdns | 2024-11-21 | 6.4 MEDIUM | N/A |
PowerDNS Authoritative Server before 2.9.21.1 drops malformed queries, which might make it easier for remote attackers to poison DNS caches of other products running on other servers, a different issue than CVE-2008-1447 and CVE-2008-3217. | |||||
CVE-2008-3217 | 1 Powerdns | 1 Recursor | 2024-11-21 | 6.8 MEDIUM | N/A |
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. | |||||
CVE-2008-1637 | 1 Powerdns | 1 Recursor | 2024-11-21 | 6.8 MEDIUM | N/A |
PowerDNS Recursor before 3.1.5 uses insufficient randomness to calculate (1) TRXID values and (2) UDP source port numbers, which makes it easier for remote attackers to poison a DNS cache, related to (a) algorithmic deficiencies in rand and random functions in external libraries, (b) use of a 32-bit seed value, and (c) choice of the time of day as the sole seeding information. | |||||
CVE-2006-4252 | 1 Powerdns | 1 Recursor | 2024-11-21 | 5.0 MEDIUM | N/A |
PowerDNS Recursor 3.1.3 and earlier allows remote attackers to cause a denial of service (resource exhaustion and application crash) via a CNAME record with a zero TTL, which triggers an infinite loop. | |||||
CVE-2006-4251 | 1 Powerdns | 1 Recursor | 2024-11-21 | 7.5 HIGH | N/A |
Buffer overflow in PowerDNS Recursor 3.1.3 and earlier might allow remote attackers to execute arbitrary code via a malformed TCP DNS query that prevents Recursor from properly calculating the TCP DNS query length. | |||||
CVE-2006-2069 | 1 Powerdns | 1 Powerdns | 2024-11-21 | 5.0 MEDIUM | N/A |
The recursor in PowerDNS before 3.0.1 allows remote attackers to cause a denial of service (application crash) via malformed EDNS0 packets. | |||||
CVE-2005-2302 | 1 Powerdns | 1 Powerdns | 2024-11-20 | 2.1 LOW | N/A |
PowerDNS before 2.9.18, when allowing recursion to a restricted range of IP addresses, does not properly handle questions from clients that are denied recursion, which could cause a "blank out" of answers to those clients that are allowed to use recursion. | |||||
CVE-2005-2301 | 1 Powerdns | 1 Powerdns | 2024-11-20 | 5.0 MEDIUM | N/A |
PowerDNS before 2.9.18, when running with an LDAP backend, does not properly escape LDAP queries, which allows remote attackers to cause a denial of service (failure to answer ldap questions) and possibly conduct an LDAP injection attack. | |||||
CVE-2005-0428 | 1 Powerdns | 1 Powerdns | 2024-11-20 | 5.0 MEDIUM | N/A |
The DNSPacket::expand method in dnspacket.cc in PowerDNS before 2.9.17 allows remote attackers to cause a denial of service by sending a random stream of bytes. | |||||
CVE-2005-0038 | 1 Powerdns | 1 Powerdns | 2024-11-20 | 5.0 MEDIUM | N/A |
The DNS implementation of PowerDNS 2.9.16 and earlier allows remote attackers to cause a denial of service via a compressed DNS packet with a label length byte with an incorrect offset, which could trigger an infinite loop. | |||||
CVE-2023-50387 | 8 Fedoraproject, Isc, Microsoft and 5 more | 13 Fedora, Bind, Windows Server 2008 and 10 more | 2024-06-10 | N/A | 7.5 HIGH |
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records. | |||||
CVE-2023-26437 | 1 Powerdns | 1 Recursor | 2024-02-04 | N/A | 5.3 MEDIUM |
Denial of service vulnerability in PowerDNS Recursor allows authoritative servers to be marked unavailable.This issue affects Recursor: through 4.6.5, through 4.7.4 , through 4.8.3. | |||||
CVE-2022-37428 | 1 Powerdns | 1 Recursor | 2024-02-04 | N/A | 6.5 MEDIUM |
PowerDNS Recursor up to and including 4.5.9, 4.6.2 and 4.7.1, when protobuf logging is enabled, has Improper Cleanup upon a Thrown Exception, leading to a denial of service (daemon crash) via a DNS query that leads to an answer with specific properties. | |||||
CVE-2022-27227 | 2 Fedoraproject, Powerdns | 3 Fedora, Authoritative Server, Recursor | 2024-02-04 | 4.3 MEDIUM | 7.5 HIGH |
In PowerDNS Authoritative Server before 4.4.3, 4.5.x before 4.5.4, and 4.6.x before 4.6.1 and PowerDNS Recursor before 4.4.8, 4.5.x before 4.5.8, and 4.6.x before 4.6.1, insufficient validation of an IXFR end condition causes incomplete zone transfers to be handled as successful transfers. |