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.
Solution:
Workaround:
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2018:0102 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2018:0487 | third party advisory vendor advisory |
https://www.debian.org/security/2018/dsa-4089 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2018:0488 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2018:0101 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1040195 | broken link third party advisory vdb entry |
https://kb.isc.org/docs/aa-01542 | vendor advisory |
http://www.securityfocus.com/bid/102716 | broken link third party advisory vdb entry |
https://lists.debian.org/debian-lts-announce/2018/01/msg00029.html | third party advisory mailing list |
https://security.netapp.com/advisory/ntap-20180117-0003/ | third party advisory |
https://supportportal.juniper.net/s/article/2018-07-Security-Bulletin-SRX-Series-Vulnerabilities-in-ISC-BIND-named | third party advisory vendor advisory |