dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-3137

HIGH · 7.5 CVSS v3.0 Published 2019-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability in BIND9 where the server incorrectly assumes a specific ordering of CNAME or DNAME records in DNS responses. When records appear in an unusual order, the server triggers an assertion failure and exits. This allows remote attackers to crash the DNS server via specially crafted responses.

MitigationUpgrade to a patched version of BIND9 (9.9.11, 9.10.6, 9.11.2 or later) or apply vendor security patches. Ensure DNS server can be restarted and test resolution after upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 6.2= 6.4= 6.5= 6.6= 7.2= 7.3= 7.4= 7.6
Enterprise Linux Server EusOperating system
Affected:= 6.7= 7.2= 7.3= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
Affected:= 6.5= 6.6= 7.2= 7.3= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Debian LinuxOperating system
Affected:= 8.0
BindApplication
Affected:= 9.9.9= 9.9.10= 9.10.4= 9.10.5= 9.11.0= 9.11.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify BIND9 is installed
    Run 'named -v' or 'rpm -q bind' (RHEL) or 'dpkg -l bind9' (Debian) to check if BIND9 is present on the system
    Affected if BIND9 is not installed or the command returns no package
  2. Determine installed BIND version
    Run 'named -v' to display the exact BIND version number
    Affected if Version is 9.9.9, 9.9.10, 9.10.4, 9.10.5, 9.11.0, or 9.11.1
  3. Confirm DNS service is running
    Run 'systemctl status named' or 'service named status' to check if the named daemon is active
    Affected if The DNS server is running and accepting queries
  4. Check if server processes external DNS responses
    Inspect named.conf for 'recursion yes;' or views that allow recursive queries from external clients
    Affected if Server provides recursive resolution to clients or processes authoritative responses from upstream servers

Environment is affected if BIND version 9.9.9 through 9.11.1 is installed and the DNS server is actively running and processing DNS queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of BIND9 (9.9.11, 9.10.6, 9.11.2 or later) or apply vendor security patches. Ensure DNS server can be restarted and test resolution after upgrade.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3137 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data