CVE-2016-6171: Knot DNS before 2.3.0 allows remote DNS servers to cause a denial of service (memory exhaustion and slave serv
CVE-2016-6171 is a high-severity flaw (CVSS 8.6) affecting knot dns. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.6 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 2.8% (top 14%) |
| CISA exploited list | No |
| Weakness | CWE-400 |
| Published | 2017-02-09 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2016-6171?
knot dns: upgrade to 2.3.0. Exact commands for each OS are on this page.
Is CVE-2016-6171 being exploited?
CVE-2016-6171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2016-6171 affect?
CVE-2016-6171 affects knot dns. Severity is high (CVSS 8.6). 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.
How urgent is CVE-2016-6171?
Priority 57/100. High severity; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2017-11104 MEDIUM 5.9 UPGRADE MITIGATE Knot DNS before 2.4.5 and 2.5.x before 2.5.2 contains a flaw within the TSIG protocol implementation that woul