CVE-2017-3145

Improper fetch cleanup sequencing in the resolver can cause named to crash

Published Jan 16, 2019 CVSS 3.1 · 7.5 High EPSS 27.7% KEV · Not listed
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.

Remediation

Vendor Solution

Upgrade to the patched release most closely related to your current version of BIND. These can all be downloaded from http://www.isc.org/downloads. BIND 9 version 9.9.11-P1 BIND 9 version 9.10.6-P1 BIND 9 version 9.11.2-P1 BIND 9 version 9.12.0rc2 BIND Supported Preview Edition is a special feature preview branch of BIND provided to eligible ISC support customers. BIND 9 version 9.9.11-S2 BIND 9 version 9.10.6-S2


Vendor Workaround

If an operator is experiencing crashes due to this, temporarily disabling DNSSEC validation can be used to avoid the known problematic code path while replacement builds are prepared.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-1255-1 bind9 security update
Debian DSA Debian DSA DSA-4089-1 bind9 security update
EUVD EUVD EUVD-2017-12286 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.
Ubuntu USN Ubuntu USN USN-3535-1 Bind vulnerability
Ubuntu USN Ubuntu USN USN-3535-2 Bind vulnerability
History
Type Values Removed Values Added
Metrics epss

{'score': 0.14308}

epss

{'score': 0.10299}

Weaknesses

Sources

Status
PUBLISHED
Assigner
isc
Published
Updated
Sep 17, 2024, 12:10 AM
Reserved
Dec 2, 2016, 12:00 AM
Status
Modified
Published
Jan 16, 2019, 8:29 PM
Modified
Jun 17, 2026, 1:17 AM
Severity
Important
Public date
Jan 16, 2018, 12:00 AM