VuXML ID | Description |
24a82876-002e-11e8-9a95-0cc47a02c232 | powerdns-recursor -- insufficient validation of DNSSEC signatures
PowerDNS Security Advisory reports:
An issue has been found in the DNSSEC validation component of
PowerDNS Recursor, allowing an ancestor delegation NSEC or NSEC3
record to be used to wrongfully prove the non-existence of a RR
below the owner name of that record. This would allow an attacker in
position of man-in-the-middle to send a NXDOMAIN answer for a name
that does exist.
Discovery 2018-01-22 Entry 2018-01-23 powerdns-recursor
< 4.1.1
CVE-2018-1000003
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-01.html
|
5418b360-29cc-11ed-a6d4-6805ca2fa271 | powerdns-recursor -- denial of service
PowerDNS Team reports:
PowerDNS Security Advisory 2022-02: incomplete exception handling related to protobuf message generation.
Discovery 2022-08-23 Entry 2022-09-01 powerdns-recursor
< 4.7.2
< 4.6.3
< 4.5.10
CVE-2022-37428
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2022-02.html
|
5418b360-29cc-11ed-a6d4-6805ca2fa271 | powerdns-recursor -- denial of service
PowerDNS Team reports:
PowerDNS Security Advisory 2022-02: incomplete exception handling related to protobuf message generation.
Discovery 2022-08-23 Entry 2022-09-01 powerdns-recursor
< 4.7.2
< 4.6.3
< 4.5.10
CVE-2022-37428
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2022-02.html
|
e9aa0e4c-ea8b-11e8-a5b7-00e04c1ea73d | powerdns-recursor -- Multiple vulnerabilities
powerdns Team reports:
CVE-2018-10851: An issue has been found in PowerDNS Recursor allowing
a malicious authoritative server to cause a memory leak by sending specially
crafted records. The issue is due to the fact that some memory is allocated
before the parsing and is not always properly released if the record is malformed.
When the PowerDNS Recursor is run inside a supervisor like supervisord or systemd,
an out-of-memory crash will lead to an automatic restart, limiting the impact to
a somewhat degraded service.
CVE-2018-14626: An issue has been found in PowerDNS Recursor allowing a remote
user to craft a DNS query that will cause an answer without DNSSEC records to be
inserted into the packet cache and be returned to clients asking for DNSSEC
records, thus hiding the presence of DNSSEC signatures for a specific qname and
qtype. For a DNSSEC-signed domain, this means that clients performing DNSSEC
validation by themselves might consider the answer to be bogus until it expires
from the packet cache, leading to a denial of service.
CVE-2018-14644: An issue has been found in PowerDNS Recursor where 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.
Discovery 2018-11-06 Entry 2018-11-17 Modified 2018-11-19 powerdns-recursor
< 4.1.7
powerdns-recursor40
< 4.0.9
https://doc.powerdns.com/recursor/changelog/4.1.html
CVE-2018-10851
CVE-2018-14626
CVE-2018-14644
|
21a854cc-cac1-11ee-b7a7-353f1e043d9a | DNSSEC validators -- denial-of-service/CPU exhaustion from KeyTrap and NSEC3 vulnerabilities
Simon Kelley reports:
If DNSSEC validation is enabled, then an attacker who can force a
DNS server to validate a specially crafted signed domain can use a
lot of CPU in the validator. This only affects dnsmasq installations
with DNSSEC enabled.
Stichting NLnet Labs reports:
The KeyTrap [CVE-2023-50387] vulnerability works by using a
combination of Keys (also colliding Keys), Signatures and number of
RRSETs on a malicious zone. Answers from that zone can force a
DNSSEC validator down a very CPU intensive and time costly
validation path.
The NSEC3 [CVE-2023-50868] vulnerability uses specially crafted responses on a
malicious zone with multiple NSEC3 RRSETs to force a DNSSEC
validator down a very CPU intensive and time costly NSEC3 hash
calculation path.
Discovery 2024-02-06 Entry 2024-02-13 Modified 2024-04-01 bind916
< 9.16.48
bind918
< 9.18.24
bind9-devel
< 9.19.21
dnsmasq
< 2.90
dnsmasq-devel
< 2.90
powerdns-recursor
< 5.0.2
unbound
< 1.19.1
FreeBSD
ge 14.0 lt 14.0_6
ge 13.2 lt 13.2_11
CVE-2023-50387
CVE-2023-50868
https://kb.isc.org/docs/cve-2023-50387
https://kb.isc.org/docs/cve-2023-50868
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
https://blog.powerdns.com/2024/02/13/powerdns-recursor-4-8-6-4-9-3-5-0-2-released
https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
SA-24:03.unbound
|
f6d6308a-f2ec-11e8-b005-6805ca2fa271 | powerdns-recursor -- Crafted query can cause a denial of service
powerdns Team reports:
CVE-2018-16855: An issue has been found in PowerDNS Recursor 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. When the PowerDNS Recursor is run inside a supervisor like supervisord or systemd, a crash will lead to an automatic restart, limiting the impact to a somewhat degraded service.
Discovery 2018-11-26 Entry 2018-12-09 powerdns-recursor
< 4.1.8
https://doc.powerdns.com/recursor/changelog/4.1.html
CVE-2018-16855
|
e15ba624-cca8-11ee-84ca-b42e991fc52e | powerdns-recursor -- Multiple Vulnerabilities
cve@mitre.org reports:
CVE-2023-50868: The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155
when RFC 9276 guidance is skipped) allows remote attackers to cause
a denial of service (CPU consumption for SHA-1 computations) via
DNSSEC responses in a random subdomain attack, aka the "NSEC3"
issue. The RFC 5155 specification implies that an algorithm must
perform thousands of iterations of a hash function in certain
situations.
CVE-2023-50387: 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.
Discovery 2024-02-14 Entry 2024-02-16 powerdns-recursor
< 5.0.2
CVE-2023-50868
https://nvd.nist.gov/vuln/detail/CVE-2023-50868
CVE-2023-50387
https://nvd.nist.gov/vuln/detail/CVE-2023-50387
|
dc33795f-ced7-11ed-b1fe-6805ca2fa271 | powerdns-recursor -- denial of service
PowerDNS Team reports:
PowerDNS Security Advisory 2023-02: Deterred spoofing attempts
can lead to authoritative servers being marked unavailable
Discovery 2023-03-29 Entry 2023-03-30 powerdns-recursor
< 4.8.4
CVE-2023-26437
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html
|
5418b360-29cc-11ed-a6d4-6805ca2fa271 | powerdns-recursor -- denial of service
PowerDNS Team reports:
PowerDNS Security Advisory 2022-02: incomplete exception handling related to protobuf message generation.
Discovery 2022-08-23 Entry 2022-09-01 powerdns-recursor
< 4.7.2
< 4.6.3
< 4.5.10
CVE-2022-37428
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2022-02.html
|
40d92cc5-1e2b-11e9-bef6-6805ca2fa271 | powerdns-recursor -- multiple vulnerabilities
PowerDNS Team reports:
CVE-2019-3806: An issue has been found in PowerDNS Recursor 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.
When the recursor is configured to run with more than one thread (threads=X) and to
do the distribution of incoming queries to the worker threads itself
(pdns-distributes-queries=yes), the Lua script is not properly loaded in the thread
handling incoming TCP queries, causing the Lua hooks to not be properly applied.
CVE-2019-3807: An issue has been found in PowerDNS Recursor 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.
Discovery 2019-01-21 Entry 2019-01-22 powerdns-recursor
< 4.1.9
https://doc.powerdns.com/recursor/changelog/4.1.html
CVE-2019-3806
CVE-2019-3807
|