Knot DNS before 2.3.0 allows remote DNS servers to cause a denial of service (memory exhaustion and slave server crash) via a large zone transfer for (1) DDNS, (2) AXFR, or (3) IXFR.

fix build on big endian

----

new upstream release, security fix for CVE-2016-6171

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ISC reports :

DNS protocols were designed with the assumption that a certain amount of trust could be presumed between the operators of primary and secondary servers for a given zone. However, in current practice some organizations have scenarios which require them to accept zone data from sources that are not fully trusted (for example: providers of secondary name service). A party who is allowed to feed data into a zone (e.g. by AXFR, IXFR, or Dynamic DNS updates) can overwhelm the server which is accepting data by intentionally or accidentally exhausting that server's memory.

ID	Name	Product	Family	Severity
94824	Fedora 25 : knot (2016-7f0fb9b38d)	Nessus	Fedora Local Security Checks	high
93057	Fedora 23 : knot (2016-66c0c2105b)	Nessus	Fedora Local Security Checks	high
93055	Fedora 24 : knot (2016-3479f8e060)	Nessus	Fedora Local Security Checks	high
92832	FreeBSD : BIND,Knot,NSD,PowerDNS -- denial over service via oversized zone transfers (7d08e608-5e95-11e6-b334-002590263bf5)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2016-6171

high

Tenable Plugins

high

high

high

high