NIC Knot Resolver 4.2.0

CPE Details

NIC Knot Resolver 4.2.0
nic
knot_resolver
4.2.0
2019-11-06
16h32 +00:00
2019-11-06
16h32 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:nic:knot_resolver:4.2.0:*:*:*:*:*:*:*

Informations

Vendor

nic

Product

knot_resolver

Version

4.2.0

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-50387 2024-02-13 23h00 +00:00 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.
7.5
High
CVE-2023-46317 2023-10-21 22h00 +00:00 Knot Resolver before 5.7.0 performs many TCP reconnections upon receiving certain nonsensical responses from servers.
7.5
High
CVE-2023-26249 2023-02-21 00h00 +00:00 Knot Resolver before 5.6.0 enables attackers to consume its resources, launching amplification attacks and potentially causing a denial of service. Specifically, a single client query may lead to a hundred TCP connection attempts if a DNS server closes connections without providing a response.
7.5
High
CVE-2022-40188 2022-09-22 22h00 +00:00 Knot Resolver before 5.5.3 allows remote attackers to cause a denial of service (CPU consumption) because of algorithmic complexity. During an attack, an authoritative server must return large NS sets or address sets.
7.5
High
CVE-2022-32983 2022-06-20 13h05 +00:00 Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters.
5.3
Medium
CVE-2021-40083 2021-08-24 22h21 +00:00 Knot Resolver before 5.3.2 is prone to an assertion failure, triggerable by a remote attacker in an edge case (NSEC3 with too many iterations used for a positive wildcard proof).
7.5
High
CVE-2020-12667 2020-05-18 22h00 +00:00 Knot Resolver before 5.1.1 allows traffic amplification via a crafted DNS answer from an attacker-controlled server, aka an "NXNSAttack" issue. This is triggered by random subdomains in the NSDNAME in NS records.
7.5
High
CVE-2019-19331 2019-12-15 23h00 +00:00 knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
7.5
High