CVE-2017-3145

published 16 Jan 2019 · updated 17 Sep 2024

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

8.0HighCVSS 7.5EPSS 28%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 28%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ISCBIND=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

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in BIND, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2017-3145 severity on Zeptric[![CVE-2017-3145](https://zeptric.io/badge/cve/CVE-2017-3145.svg)](https://zeptric.io/cve/CVE-2017-3145)