Skip to main content
No exploitation reported

CVE-2017-3137

No exploitation reported by the sources we read.

  • Published2019-01-16
  • WeaknessCWE-617

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

Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.

Timeline

dates in UTC
  1. 2019-01-1620:29CVE publishedNVD

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-3137?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-3137?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Redhat enterprise linux server aus
BranchAffectedFixed in
6.2= 6.2no fix published
6.4= 6.4no fix published
6.5= 6.5no fix published
6.6= 6.6no fix published
7.2= 7.2no fix published
7.3= 7.3no fix published
7.4= 7.4no fix published
7.6= 7.6no fix published
Isc bind
BranchAffectedFixed in
9.9= 9.9.9no fix published
9.9= 9.9.10no fix published
9.10= 9.10.4no fix published
9.10= 9.10.5no fix published
9.11= 9.11.0no fix published
9.11= 9.11.1no fix published
Redhat enterprise linux server eus
BranchAffectedFixed in
6.7= 6.7no fix published
7.2= 7.2no fix published
7.3= 7.3no fix published
7.4= 7.4no fix published
7.5= 7.5no fix published
7.6= 7.6no fix published

8 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

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CNACVSS 3.07.5read 2026-10-23
  • NVDCVSS 3.07.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-617read 2026-10-23
  • FIRST EPSSEPSS score9.0 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.0/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-3137?

Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.

Is CVE-2017-3137 actively exploited?

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

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

CVE-2017-3137 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/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 productCISA KEV additions, October 2026Search CVEs

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

Go further

Related vulnerabilities

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

Back to CVE Database