dbcve.org
FedoraOperating system · Fedoraproject

CVE-2016-1286

HIGH · 8.6 CVSS v3.1 Published 2016-03-09
Fix available
A fix is available. Upgrade to 9.9.8 / 9.10.3 or later.
See remediation →
95/100
Remediation priority · Urgent
High EPSS 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
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to db.c and resolver.c.

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

ISC BIND 9 versions before 9.9.8-P4 and 9.10.x before 9.10.3-P4 contain a denial of service vulnerability where a remote attacker can send a specially crafted DNS signature record for a DNAME record, triggering an assertion failure in db.c or resolver.c that causes the named daemon to exit.

MitigationUpgrade BIND 9 to version 9.9.8-P4 or 9.10.3-P4 or later. If immediate patching is not possible, consider restricting zone transfers or limiting recursion to trusted clients as a temporary measure.

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
FedoraOperating system
Affected:= 22= 23= 24
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.10
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0
BindApplication
Affected:>= 9.0.0, < 9.9.8>= 9.10.0, < 9.10.3= 9.9.8= 9.10.3
Linux Enterprise DebuginfoApplication
Affected:= 11
ManagerApplication
Affected:= 2.1
Manager ProxyApplication
Affected:= 2.1
Openstack CloudApplication
Affected:= 5

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 installation and version
    Run 'named -v' or 'named -V' to display the BIND version, or check the package manager: 'rpm -q bind' (RHEL/CentOS), 'dpkg -l bind9' (Debian/Ubuntu), or 'dnf list installed bind' (Fedora)
    Affected if Version is 9.0.0 through 9.9.8, or 9.10.0 through 9.10.3 (including 9.9.8 and 9.10.3 themselves)
  2. Confirm the named daemon is running
    Run 'ps aux | grep named' or 'systemctl status named' to check if the BIND named daemon is active
    Affected if The named process is actively running and serving DNS queries
  3. Check if recursive queries or zone transfers are permitted
    Inspect the named.conf configuration file (typically at /etc/bind/named.conf or /etc/named.conf) for 'allow-recursion' or 'allow-transfer' directives; run 'named-checkconf -z /etc/named.conf' to validate configuration
    Affected if The server accepts recursive queries from untrusted clients or allows zone transfers, enabling remote attackers to send malicious DNAME records
  4. Verify DNAME record processing is enabled
    DNAME processing is enabled by default in BIND 9; check configuration for any 'disable-empty-zone' or 'fetch-glue' options that might alter DNAME handling; review zone files for existing DNAME records with 'dig +short dname.example.com @localhost DNS'
    Affected if DNAME record processing is active (default state), which is required for the assertion failure to be triggered

Your environment is affected if BIND version 9.0.0-9.9.8 or 9.10.0-9.10.3 is installed and the named daemon is running with network exposure to untrusted clients.

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 9.9.8 / 9.10.3 or later
Fixed in 9.9.89.10.3
Interim mitigation

Upgrade BIND 9 to version 9.9.8-P4 or 9.10.3-P4 or later. If immediate patching is not possible, consider restricting zone transfers or limiting recursion to trusted clients as a temporary measure.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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