dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-3135

MEDIUM · 5.9 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 →
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
Under some conditions when using both DNS64 and RPZ to rewrite query responses, query processing can resume in an inconsistent state leading to either an INSIST assertion failure or an attempt to read through a NULL pointer. Affects BIND 9.8.8, 9.9.3-S1 -> 9.9.9-S7, 9.9.3 -> 9.9.9-P5, 9.9.10b1, 9.10.0 -> 9.10.4-P5, 9.10.5b1, 9.11.0 -> 9.11.0-P2, 9.11.1b1.

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

In BIND 9, when both DNS64 and RPZ (Response Policy Zones) are configured together to rewrite query responses, certain conditions can cause query processing to resume in an inconsistent state. This leads to either an INSIST assertion failure (program crash due to failed internal check) or a NULL pointer dereference attempt, causing denial of service.

MitigationUpgrade to a patched BIND 9 version beyond the affected ranges, or if immediate patching is not feasible, consider disabling either DNS64 or RPZ functionality until the upgrade can be performed.

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:= 7.0
Enterprise Linux ServerOperating system
Affected:= 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:= 7.0
Debian LinuxOperating system
Affected:= 8.0= 9.0
BindApplication
Affected:= 9.9.3= 9.9.8= 9.9.9= 9.9.10= 9.10.0= 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 9 version
    Run 'named -v' or 'named -V' to get the BIND version, or use 'rpm -q bind' (RHEL) or 'dpkg -l bind9' (Debian)
    Affected if Version matches one of the affected ranges: 9.9.3, 9.9.8-9.9.10, 9.10.0, 9.10.4-9.10.5, 9.11.0-9.11.1, or is the RHEL/Debian versions listed (7.0, 7.3-7.6, 8.0, 9.0)
  2. Locate BIND configuration file
    Check for named.conf at /etc/named.conf, /etc/bind/named.conf, or paths specified in the named startup configuration
    Affected if Configuration file exists and contains BIND settings
  3. Verify DNS64 configuration
    Search the named.conf file (and included files) for the 'dns64' directive. Run: grep -r 'dns64' /etc/named.conf /etc/bind/ 2>/dev/null
    Affected if The 'dns64' block or option is present in the configuration
  4. Verify RPZ configuration
    Search the named.conf file (and included files) for 'response-policy' or 'rpz' directives. Run: grep -r 'response-policy\|rpz' /etc/named.conf /etc/bind/ 2>/dev/null
    Affected if The 'response-policy' zone configuration or RPZ-related options are present
  5. Confirm both features are enabled together
    Review the configuration to confirm that both DNS64 and RPZ are simultaneously configured and active
    Affected if Both DNS64 and RPZ are found enabled in the same BIND configuration

Environment is affected if running a vulnerable BIND 9 version (9.9.3, 9.9.8-9.9.10, 9.10.0, 9.10.4-9.10.5, 9.11.0-9.11.1 or equivalent RHEL/Debian) AND has both DNS64 and RPZ features enabled simultaneously in the configuration.

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 BIND 9 version beyond the affected ranges, or if immediate patching is not feasible, consider disabling either DNS64 or RPZ functionality until the upgrade can be performed.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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