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).
An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
The product does not release or incorrectly releases a resource before it is made available for re-use.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19331 | issue tracking exploit patch |
| https://www.knot-resolver.cz/2019-12-04-knot-resolver-4.3.0.html | release notes vendor advisory |
| https://lists.debian.org/debian-lts-announce/2024/04/msg00017.html | mailing list |