No exploitation reported

CVE-2017-3145

No exploitation reported by the sources we read.

Published2019-01-16
WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC

2019-01-1620:29CVE publishedNVD
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-3145?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-3145?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Isc bind

Branch	Affected	Fixed in	Source
9.x	≥ 9.4.0, ≤ 9.8.8	no fix published	NVD
9.9	≥ 9.9.0, ≤ 9.9.11	no fix published	NVD
9.10	≥ 9.10.0, ≤ 9.10.6	no fix published	NVD
9.11	≥ 9.11.0, ≤ 9.11.2	no fix published	NVD
9.9	= 9.9.3	no fix published	NVD
9.9	= 9.9.11	no fix published	NVD
9.10	= 9.10.5	no fix published	NVD
9.10	= 9.10.6	no fix published	NVD
9.12	= 9.12.0	no fix published	NVD

Redhat enterprise linux server aus

Branch	Affected	Fixed in	Source
6.4	= 6.4	no fix published	NVD
6.5	= 6.5	no fix published	NVD
6.6	= 6.6	no fix published	NVD
7.2	= 7.2	no fix published	NVD
7.3	= 7.3	no fix published	NVD
7.4	= 7.4	no fix published	NVD
7.6	= 7.6	no fix published	NVD

Juniper junosversion to verify

Branch	Affected	Fixed in	Source
12.1	= 12.1x46-d76	no fix published	NVD
12.3	= 12.3x48-d70	no fix published	NVD
15.1	= 15.1x49-d140	no fix published	NVD
17.4	= 17.4r2	no fix published	NVD
18.1	= 18.1r2	no fix published	NVD
18.2	= 18.2r1	no fix published	NVD

7 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

kb.isc.orgVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.17.5read 2026-10-23
CNACVSS 3.07.5read 2026-10-23
NVDCVSS 2.05read 2026-10-23
NVDweakness (CWE)CWE-416read 2026-10-23
FIRST EPSSEPSS score27.9 %read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2019-01-16
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-3145?

Is CVE-2017-3145 actively exploited?

Active exploitation of CVE-2017-3145 has not been confirmed. Its EPSS score was 27.9% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-3145?

CVE-2017-3145 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database