CVE-2020-8617

Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.

Data as of 2 Nov 2026 · NVD, CISA KEV, EPSS

Defenders still triage vulnerabilities one CVE at a time, while increasingly automated attackers combine them at machine speed. Omenwave models the plausible pathways by which this CVE could be chained with others — surfacing them for research and awareness, with evidence for each step.

Kill-chain stage

IMPACT

Requires

NONE access, NETWORK vector

Grants

NONE access (terminal impact)

Capabilities

denial of service

Model confidence

high · CVSS 3.1

No plausible forward hops are modelled from this CVE in the current corpus (it may be a terminal impact, or an independent entry point rather than a continuation).