ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2016-1285

named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attacke…

Published Mar 9, 2016 · catalog updated Jun 17, 2026 · the affected product

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check this week

CVE-2016-1285 is not in CISA KEV. FIRST estimates a 57.83% chance of exploitation in the next 30 days. Check whether you run the affected product.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
57.83%
Remediation
Version ranges on file
Affected products
cpe isc/bind

named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe isc/bind9.9.8
  • cpe isc/bind< 9.10.3
  • cpe isc/bind< 9.9.8

How to fix CVE-2016-1285

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2016-1285 is not in CISA KEV. FIRST estimates a 57.83% chance of exploitation in the next 30 days. Check whether you run the affected product.

Which versions are affected?

Compare what you have installed with 9.9.8, < 9.10.3, < 9.9.8. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 57.83%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 9, 2016 · Monitored products — high

    Detected

    named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.

  2. Jun 17, 2026 · Monitored products — high

    Updated

    named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.

Sources

  • CVE.orgVulnerability recordCVE-2016-1285

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2016-1285

    named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 7, 2026
  • Monitored products — highNov 6, 2026