While handling a particular type of malformed packet BIND erroneously selects a SERVFAIL rcode instead of a FORMERR rcode. If the receiving view has the SERVFAIL cache feature enabled, this can trigger an assertion failure in badcache.c when the request doesn't contain all of the expected information. Affects BIND 9.10.5-S1 to 9.10.5-S4, 9.10.6-S1, 9.10.6-S2.
References
Link | Resource |
---|---|
https://kb.isc.org/docs/aa-01562 | Vendor Advisory |
https://security.netapp.com/advisory/ntap-20180926-0005/ | Third Party Advisory |
http://www.securitytracker.com/id/1040438 | Third Party Advisory VDB Entry |
http://www.securityfocus.com/bid/103189 | Third Party Advisory VDB Entry |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2019-01-16 12:29
Updated : 2019-10-09 16:41
NVD link : CVE-2018-5734
Mitre link : CVE-2018-5734
JSON object : View
CWE
CWE-617
Reachable Assertion
Products Affected
netapp
- data_ontap_edge
- solidfire_element_os_management_node
isc
- bind