Show filters
3 Total Results
Displaying 1-3 of 3
Sort by:
Attacker Value
Unknown
Improper fetch cleanup sequencing in the resolver can cause named to crash
Disclosure Date: January 16, 2019 (last updated November 27, 2024)
BIND was improperly sequencing cleanup operations on upstream recursion fetch contexts, leading in some cases to a use-after-free error that can trigger an assertion failure and crash in named. Affects BIND 9.0.0 to 9.8.x, 9.9.0 to 9.9.11, 9.10.0 to 9.10.6, 9.11.0 to 9.11.2, 9.9.3-S1 to 9.9.11-S1, 9.10.5-S1 to 9.10.6-S1, 9.12.0a1 to 9.12.0rc1.
0
Attacker Value
Unknown
CVE-2016-1285
Disclosure Date: March 09, 2016 (last updated December 01, 2023)
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.
0
Attacker Value
Unknown
CVE-2016-1286
Disclosure Date: March 09, 2016 (last updated December 01, 2023)
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to db.c and resolver.c.
0
