Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.
Solution:
Workaround:
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2017:1095 | third party advisory vendor advisory |
https://security.gentoo.org/glsa/201708-01 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1038258 | third party advisory vdb entry |
https://security.netapp.com/advisory/ntap-20180802-0002/ | third party advisory |
http://www.securitytracker.com/id/1040195 | third party advisory vdb entry |
https://access.redhat.com/errata/RHSA-2017:1582 | third party advisory vendor advisory |
https://www.debian.org/security/2017/dsa-3854 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1583 | third party advisory vendor advisory |
http://www.securityfocus.com/bid/97651 | third party advisory vdb entry |
https://access.redhat.com/errata/RHSA-2017:1105 | third party advisory vendor advisory |
https://kb.isc.org/docs/aa-01466 | vendor advisory |