7.5
High
CVE-2017-3145 BIND was improperly sequencing cleanup operations on upstream recursion fetch contexts, leading in some cases to a…
Description
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| BIND 9 | Versions not published |
References
- RHSA-2018:0102 access.redhat.com
- RHSA-2018:0487 access.redhat.com
- DSA-4089 www.debian.org
- RHSA-2018:0488 access.redhat.com
- RHSA-2018:0101 access.redhat.com
- 1040195 www.securitytracker.com
- kb.isc.org kb.isc.org
- 102716 www.securityfocus.com
- [debian-lts-announce] 20180121 [SECURITY] [DLA 1255-1] bind9 security update lists.debian.org
- security.netapp.com security.netapp.com
- supportportal.juniper.net supportportal.juniper.net
Timeline
- Published
- Last modified
Other CVEs of BIND 9
The 87 CVEs of BIND 9 →
CVE-2026-97313
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may…
7.5
High
CVE-2026-96888
A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an…
7.5
High
CVE-2026-94300
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`"
8.1
High
CVE-2026-19630
In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with…
7.5
High