knot-resolver before version 4.3.0 is vulnerable to...
High severity
Unreviewed
Published
May 24, 2022
to the GitHub Advisory Database
•
Updated Apr 26, 2024
Description
Published by the National Vulnerability Database
Dec 16, 2019
Published to the GitHub Advisory Database
May 24, 2022
Last updated
Apr 26, 2024
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).
References