CVE-2017-11104
What it is
Knot DNS before 2.4.5 and 2.5.x before 2.5.2 contains a flaw within the TSIG protocol implementation that would allow an attacker with a valid key name and algorithm to bypass TSIG authentication if no additional ACL restrictions are set, because of an improper TSIG validity period check.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering.
- Exploit odds
- 2.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.7% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.7% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- knot-dns Knot Dns ≤ 2.4.4
- knot-dns Knot Dns 2.5.0
- knot-dns Knot Dns 2.5.1
- Debian Linux 8.0
- Debian Linux 9.0
- Debian Linux 10.0
Attack profile CVSS 3.1 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-11104.md and follow it. Check whether this project is affected by CVE-2017-11104. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
- https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
- http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
- https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
References
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00076.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00078.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00089.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00049.html
- http://www.debian.org/security/2017/dsa-3910
- http://www.securityfocus.com/bid/99598
- http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
- https://bugs.debian.org/865678
- https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00076.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00078.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00089.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00049.html
- http://www.debian.org/security/2017/dsa-3910
- http://www.securityfocus.com/bid/99598
- http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
- https://bugs.debian.org/865678
- https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html