CVE-2016-1285

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

57.8% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2016-03-09 23:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:41 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 57.8% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2016-03-09 23:59 UTC

Last modified

2026-06-17 00:41 UTC

Exploit probability

57.8% · EPSS, next 30 days

Record status

Modified

Affected

• Isc Bind < 9.9.8
• Isc Bind < 9.10.3
• Isc Bind 9.9.8
• Isc Bind 9.10.3
• Suse Linux Enterprise Debuginfo 11
• Suse Manager 2.1
• Suse Manager Proxy 2.1
• Suse Openstack Cloud 5

Attack profile CVSS 3.1 · 6.8

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-1285.md and follow it. Check whether this project is affected by CVE-2016-1285. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge