dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-3136

MEDIUM · 5.9 CVSS v3.0 Published 2019-01-16
Fix available
A fix is available. Upgrade to after 9.10.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS64 feature and other preconditions were met. Affects BIND 9.8.0 -> 9.8.8-P1, 9.9.0 -> 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.0 -> 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0 -> 9.11.0-P3, 9.11.1b1->9.11.1rc1, 9.9.3-S1 -> 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 specially crafted DNS query with specific characteristics can trigger an assertion failure in BIND servers configured to use DNS64, causing the server to terminate. This is a denial-of-service vulnerability exploitable remotely when DNS64 is enabled.

MitigationUpgrade to a patched BIND version (9.8.8-P2, 9.9.9-P7, 9.10.4-P7, 9.10.5b1, 9.11.0-P4, or later) or disable DNS64 if not required.

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:= 7.3= 7.4= 7.6
Enterprise Linux Server EusOperating system
Affected:= 7.3= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
Affected:= 7.3= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Debian LinuxOperating system
Affected:= 8.0
BindApplication
Affected:>= 9.8.0, <= 9.8.8>= 9.9.0, <= 9.9.9>= 9.10.0, <= 9.10.4= 9.8.0= 9.9.0= 9.9.3= 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/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 BIND installation and version
    Run 'named -v' or 'named -V' to display the BIND version, or check the package manager (e.g., 'rpm -q bind' on RHEL, 'dpkg -l bind9' on Debian)
    Affected if The installed version falls within any of these ranges: 9.8.0-9.8.8, 9.9.0-9.9.9, 9.10.0-9.10.4, or matches specific versions 9.8.0, 9.9.0, 9.9.3, 9.9.10, 9.10.4, 9.10.5, 9.11.0, 9.11.1
  2. Locate BIND configuration files
    Check common configuration locations such as /etc/named.conf, /etc/bind/named.conf, or the file specified with 'named -c' option
    Affected if Unable to locate the active named configuration file
  3. Verify if DNS64 is enabled
    Search the named configuration file for 'dns64' directives. Use 'grep -i dns64 /path/to/named.conf' to find DNS64 blocks
    Affected if DNS64 blocks or directives are present in the configuration, indicating DNS64 is enabled
  4. Check for DNS64 synthesis prefix
    Within DNS64 blocks in the configuration, look for the 'clients' or 'synthesized' directives that define which client prefixes are affected
    Affected if DNS64 is enabled with any prefix configuration - the vulnerability applies to any DNS64 synthesis

The environment is affected if BIND version is in the affected ranges AND DNS64 is actively enabled in the configuration, as the assertion failure only triggers when DNS64 processes a specially crafted query.

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.10.4
Interim mitigation

Upgrade to a patched BIND version (9.8.8-P2, 9.9.9-P7, 9.10.4-P7, 9.10.5b1, 9.11.0-P4, or later) or disable DNS64 if not required.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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