Skip to content
Snippets Groups Projects
Commit b99dd3a6 authored by Aleš Mrázek's avatar Aleš Mrázek
Browse files

Merge branch 'release-5.7.1' into 'master'

release 5.7.1

See merge request !121
parents c66fab68 3d21d741
1 merge request!121release 5.7.1
Pipeline #122156 passed with stages
in 11 seconds
:title: Knot Resolver 5.7.1 released
:slug: knot-resolver-5.7.1
:date: 2024-02-13 14:30
:lang: en
Security
--------
- CVE-2023-50868: NSEC3 closest encloser proof can exhaust CPU
- validator: lower the NSEC3 iteration limit (150 -> 50)
- validator: similarly also limit excessive NSEC3 salt length
- cache: limit the amount of work on SHA1 in NSEC3 aggressive cache
- validator: limit the amount of work on SHA1 in NSEC3 proofs
- validator: refuse to validate answers with more than 8 NSEC3 records
- CVE-2023-50387 "KeyTrap": DNSSEC verification complexity
could be exploited to exhaust CPU resources and stall DNS resolvers.
Solution boils down mainly to limiting crypto-validations per packet.
We would like to thank Elias Heftrig, Haya Schulmann, Niklas Vogel and Michael Waidner
from the German National Research Center for Applied Cybersecurity ATHENE
for bringing this vulnerability to our attention.
Improvements
------------
- update addresses of B.root-servers.net (!1478)
Bugfixes
--------
- fix potential SERVFAIL deadlocks if net.ipv6 = false (#880)
......@@ -85,9 +85,9 @@ Source code
===========
- `Knot Resolver
5.7.0 <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.0.tar.xz>`__
(`asc <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.0.tar.xz.asc>`__,
`sha256 <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.0.tar.xz.sha256>`__)
5.7.1 <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.1.tar.xz>`__
(`asc <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.1.tar.xz.asc>`__,
`sha256 <https://secure.nic.cz/files/knot-resolver/knot-resolver-5.7.1.tar.xz.sha256>`__)
- `Old releases <https://secure.nic.cz/files/knot-resolver/?C=N;O=D>`__
New releases are signed with one of our developer PGP keys:
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment