Nic Knot Resolver vulnerabilities

15 vulnerabilities

Known vulnerabilities in Nic Knot Resolver, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

7.5CVE-2018-1110debianknot-resolver+2
EPSS score
1.24%
A flaw was found in knot-resolver before version 2.3.0. Malformed DNS messages may cause denial of service.
4.3CVE-2018-1000002debianknot-resolver+1
EPSS score
1.08%
Improper input validation bugs in DNSSEC validators components in Knot Resolver (prior version 1.5.2) allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay.
7.5CVE-2018-10920cz.nicknot-resolver+3
EPSS score
3.24%
Improper input validation bug in DNS resolver component of Knot Resolver before 2.4.1 allows remote attacker to poison cache.
5.9CVE-2013-5661iscbind+3
EPSS score
3.45%
Cache Poisoning issue exists in DNS Response Rate Limiting.
7.5CVE-2021-40083debianknot-resolver+2
EPSS score
1.42%
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.5CVE-2020-12667debianknot-resolver+2
EPSS score
2.61%
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.5CVE-2022-40188debianknot-resolver+4
EPSS score
1.95%
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.
5.3CVE-2022-32983debianknot-resolver+2
EPSS score
0.74%
Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters.
7.5CVE-2019-19331cz.nicknot-resolver+4
EPSS score
2.11%
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.5CVE-2019-10190cz.nicknot-resolver+4
EPSS score
1.99%
A vulnerability was discovered in DNS resolver component of knot resolver through version 3.2.0 before 4.1.0 which allows remote attackers to bypass DNSSEC validation for non-existence answer. NXDOMAIN answer would get passed through to the client even if its DNSSEC validation failed, instead of sending a SERVFAIL packet. Caching is not affected by this particular bug but see CVE-2019-10191.
7.5CVE-2019-10191cz.nicknot-resolver+4
EPSS score
1.93%
A vulnerability was discovered in DNS resolver of knot resolver before version 4.1.0 which allows remote attackers to downgrade DNSSEC-secure domains to DNSSEC-insecure state, opening possibility of domain hijack using attacks against insecure DNS protocol.
8.1CVE-2026-66374debianknot-resolver+2
EPSS score
0.62%
Knot Resolver before 6.4.1 allows remote code execution via a heap-based buffer overflow in the DoQ (DNS-over-QUIC) receive path.
7.5CVE-2023-26249debianknot-resolver+2
EPSS score
0.71%
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.5CVE-2023-46317debianknot-resolver+2
EPSS score
0.64%
Knot Resolver before 5.7.0 performs many TCP reconnections upon receiving certain nonsensical responses from servers.
7.5CVE-2023-50387alpinebind+33
EPSS score
99.99%
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.