CVE-2021-40083
Published: 25 August 2021
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).
Notes
Author | Note |
---|---|
ccdm94 | this issue seems to have been introduced by commit 7107faeb (5.3.1). Therefore, versions that do not include this commit will not be vulnerable. |
Priority
Status
Package | Release | Status |
---|---|---|
knot-resolver Launchpad, Ubuntu, Debian |
bionic |
Not vulnerable
(code not present)
|
focal |
Not vulnerable
(code not present)
|
|
impish |
Ignored
(end of life)
|
|
kinetic |
Not vulnerable
(5.5.1-5)
|
|
lunar |
Not vulnerable
(5.6.0-1)
|
|
trusty |
Does not exist
|
|
xenial |
Not vulnerable
(code not present)
|
|
upstream |
Released
(5.3.2)
|
|
hirsute |
Ignored
(end of life)
|
|
jammy |
Not vulnerable
(5.4.4-1)
|
|
Patches: upstream: https://gitlab.nic.cz/knot/knot-resolver/-/commit/97ec93e178207699f438a8300eecabc2654ae76f |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |