PT-2022-25268 · Unknown +4 · Knot Resolver +4

Name of the Vulnerable Software and Affected Versions: Knot Resolver versions prior to 5.5.3 Description: The issue allows remote attackers to cause a denial of service due to algorithmic complexity, resulting in CPU consumption. This occurs when an authoritative server returns large NS sets or...

CVE-2022-40188: Inefficient Algorithmic Complexity

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...

CVE-2022-40188

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...

CVE-2022-40188

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...

CVE-2022-40188

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...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

DEBIAN-CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

Design/Logic Flaw

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

UBUNTU-CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

The CVE-2022-32983 issue affects Knot Resolver up to version 5.5.1, where DNS cache poisoning could occur when an attempt is made to limit forwarding actions by filters. Root cause details in connected sources indicate a vulnerability in handling forwarding/filter constraints that can lead to cac...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

CVE-2022-32983: Authentication Bypass by Spoofing

Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters...

Knot Resolver 安全漏洞

Knot Resolver is a caching DNS resolver implementation that includes a resolver library and daemon. A security vulnerability exists in Knot Resolver versions prior to 5.5.1, which stems from a possible DNS cache poisoning when attempting to limit forwarding operations via a filter...

PT-2022-21620 · Unknown +2 · Knot Resolver +2

Name of the Vulnerable Software and Affected Versions: Knot Resolver versions through 5.5.1 Description: The issue may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters. Recommendations: For versions through 5.5.1, update to a version that contains a fix fo...

CVE-2019-10190

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...