VuXML ID | Description |
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
|
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
|
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
|
641cd669-bc37-11ea-babf-6805ca2fa271 | powerdns-recursor -- access restriction bypass
PowerDNS Team reports:
CVE-2020-14196: An issue has been found in PowerDNS Recursor where the ACL applied to the internal
web server via webserver-allow-from is not properly enforced, allowing a remote attacker to send
HTTP queries to the internal web server, bypassing the restriction.
In the default configuration the API webserver is not enabled. Only installations using a
non-default value for webserver and webserver-address are affected.
Discovery 2020-07-01 Entry 2020-07-02 powerdns-recursor
ge 4.3.0 lt 4.3.2
ge 4.2.0 lt 4.2.3
ge 4.1.0 lt 4.1.17
https://doc.powerdns.com/recursor/security-advisories/index.html
CVE-2020-14196
|
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
|
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
|
a6860b11-0dee-11eb-94ff-6805ca2fa271 | powerdns-recursor -- cache pollution
PowerDNS Team reports:
CVE-2020-25829: An issue has been found in PowerDNS Recursor where 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 in a denial
of service for installations that always validate (dnssec=validate)
and for clients requesting validation when on-demand validation is
enabled (dnssec=process).
Discovery 2020-10-13 Entry 2020-10-14 powerdns-recursor
ge 4.3.0 lt 4.3.5
ge 4.2.0 lt 4.2.5
ge 4.1.0 lt 4.1.18
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2020-07.html
CVE-2020-25829
|
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
|
f9c5a410-9b4e-11ea-ac3f-6805ca2fa271 | powerdns-recursor -- multiple vulnerabilities
PowerDNS Team reports:
CVE-2020-10995: 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 by an authoritative name server to amplify the resulting traffic between the recursive and
other authoritative name servers. Both types of service can suffer degraded performance as an effect.
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. This would allow an attacker in position of man-in-the-middle to send a
NXDOMAIN answer for a name that does exist, bypassing DNSSEC validation.
CVE-2020-10030: An issue has been found in PowerDNS Authoritative Server allowing 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
not null-terminate the returned string if the hostname is larger than the supplied buffer. Linux
systems are not affected because the buffer is always large enough. OpenBSD systems are not affected
because the returned hostname is always null-terminated. Under some conditions this issue can lead
to the writing of one null-byte out-of-bounds on the stack, causing a denial of service or possibly
arbitrary code execution.
Discovery 2020-05-19 Entry 2020-05-26 Modified 2020-05-29 powerdns-recursor
ge 4.3.0 lt 4.3.1
ge 4.2.0 lt 4.2.2
ge 4.1.0 lt 4.1.16
https://doc.powerdns.com/recursor/security-advisories/index.html
CVE-2020-10995
CVE-2020-12244
CVE-2020-10030
|
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
|