dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-3145

HIGH · 7.5 CVSS v3.1 Published 2019-01-16
Fix available
A fix is available. Upgrade to after 9.11.2 or later.
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
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.

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

BIND DNS server contains a use-after-free vulnerability in its upstream recursion fetch context cleanup sequencing. Improper ordering of cleanup operations can cause memory to be accessed after being freed, leading to an assertion failure and crash of the named daemon.

MitigationUpgrade to BIND 9.9.12, 9.10.7, 9.11.3, 9.12.0, or later versions. As a workaround, disable recursion on authoritative servers or limit query sources.

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.4= 6.5= 6.6= 7.2= 7.3= 7.4= 7.6
Enterprise Linux Server EusOperating system
Affected:= 6.7= 7.3= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
Affected:= 6.6= 7.2= 7.3= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0
BindApplication
Affected:>= 9.4.0, <= 9.8.8>= 9.9.0, <= 9.9.11>= 9.10.0, <= 9.10.6>= 9.11.0, <= 9.11.2= 9.9.3= 9.9.11= 9.10.5= 9.10.6= 9.12.0

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.1/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. Identify the installed BIND version
    Run 'named -v' or 'named -V' to display the BIND version. On RHEL/Debian, also check via 'rpm -q bind' or 'dpkg -l bind9'.
    Affected if The installed version falls within: 9.4.0-9.8.8, 9.9.0-9.9.11, 9.10.0-9.10.6, 9.11.0-9.11.2, or is exactly 9.9.3, 9.9.11, 9.10.5, 9.10.6, 9.12.0. For RHEL 6/7 or Debian 7/8/9, the base bind versions in those distributions are also affected.
  2. Verify if recursion is enabled in named.conf
    Inspect the BIND configuration file (typically /etc/named.conf or /etc/bind/named.conf.options) and look for 'recursion yes;' or 'allow-recursion { ... };' statements.
    Affected if Recursion is set to 'yes' or allowed without restrictive ACLs, making the server vulnerable to recursion-based attacks.
  3. Confirm the server handles recursive queries
    Check if the server is configured as a recursive resolver. Look for 'recursion yes;' in options, and verify the server responds to recursive queries from clients.
    Affected if The server accepts and processes recursive queries from clients, which is required for the vulnerable code path to be exercised.
  4. Identify the operating system and version
    Run 'cat /etc/os-release' or 'uname -a' to determine the OS. For RHEL systems, check 'cat /etc/redhat-release'.
    Affected if Running RHEL 6.0, 7.0, 6.4, 6.5, 6.6, 6.7, 7.2, 7.3, 7.4, 7.5, 7.6 or Debian 7.x, 8.x, 9.x with the bundled BIND version.

You are affected if your BIND version is within the listed vulnerable ranges AND your server is configured to handle recursive queries (the vulnerability exists in the recursion fetch context cleanup code path).

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
Upgrade available Upgrade to a release after 9.11.2
Interim mitigation

Upgrade to BIND 9.9.12, 9.10.7, 9.11.3, 9.12.0, or later versions. As a workaround, disable recursion on authoritative servers or limit query sources.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3145 — 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-3145 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