named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is in the named daemon of ISC BIND 9.x (before 9.9.8-P4) and 9.10.x (before 9.10.3-P4), where DNAME records are not properly handled while parsing fetch reply messages. An attacker who can send a malformed packet to the rndc control channel interface can trigger an assertion failure that causes the daemon to exit, resulting in denial of service.
Official description · CVE.org
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 9 Mar 2016. No public exploit code or confirmed exploitation is recorded.