CVE-2017-3139

HIGHNVD 7.57.5—

7.5

A denial of service flaw was found in the way BIND handled DNSSEC validation. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 72.8%
KEV: Not listed

Published

April 9, 2019

Last Modified

November 21, 2024

References (4)

security-officer@ischttps://access.redhat.com/security/cve/cve-2017-3139
security-officer@ischttps://bugzilla.redhat.com/show_bug.cgi?id=1447743
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/security/cve/cve-2017-3139
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=1447743

Patch Availability(2)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
redhat	bind-32:9.8.2-0.37.rc1.el6_7.11	2017-06-28	redhat
redhat	bind-32:9.8.2-0.62.rc1.el6_9.2	2017-05-08	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-617

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 20:46 UTCEG score recompute
2026-05-27 20:46 UTCVendor advisory
2026-05-27 20:46 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-23 04:04 UTCOSV refresh

Frequently asked(5)

What is CVE-2017-3139?

CVE-2017-3139 is a high vulnerability published on April 9, 2019. A denial of service flaw was found in the way BIND handled DNSSEC validation. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response.

When was CVE-2017-3139 disclosed?

CVE-2017-3139 was first published in the National Vulnerability Database on April 9, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-3139 actively exploited?

CVE-2017-3139 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 72.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-3139?

CVE-2017-3139 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2017-3139?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3139, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3139

Explore →

Is Your Infrastructure Affected by CVE-2017-3139?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs