Vulnerabilities

Vulnerability · 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

Published May 19, 2020 · catalog updated Oct 26, 2026 · Using a specially-crafted message,

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

Check this week

CVE-2020-8617 is not in CISA KEV. FIRST estimates a 93.33% chance of exploitation in the next 30 days. Check whether you run Using a specially-crafted message,.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Using a specially-crafted message,).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
93.33%
Remediation
Advisory link
Affected products
Alpine:v3.10 bind · Alpine:v3.11 bind · Alpine:v3.12 bind · Alpine:v3.13 bind · Alpine:v3.14 bind · Alpine:v3.15 bind

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.

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.

  • Alpine:v3.10 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.11 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.12 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.13 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.14 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.15 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.16 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.17 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.18 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.19 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.20 bind9.0.0 → 9.14.12-r0
  • Alpine:v3.21 bind9.0.0 → 9.14.12-r0
  • Debian:12 bind90 → 1:9.16.3-1
  • Debian:13 bind90 → 1:9.16.3-1
  • Debian:14 bind90 → 1:9.16.3-1

How to fix CVE-2020-8617

What to do

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

Should you patch?

CVE-2020-8617 is not in CISA KEV. FIRST estimates a 93.33% chance of exploitation in the next 30 days. Check whether you run Using a specially-crafted message,.

Which versions are affected?

Compare what you have installed with 9.0.0 → 9.14.12-r0, 0 → 1:9.16.3-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 93.33%. There is no CISA KEV listing. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.

Technology hubs

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. May 19, 2020 · OpenSSF OSV / OSV Scanner

    Detected

    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 d

  2. Sep 11, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    bind9 fixed in 1:9.16.3-1; bind9 fixed in 1:9.16.3-1; bind9 fixed in 1:9.16.3-1

  3. Sep 11, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    bind9 fixed in 1:9.16.3-1

  4. Sep 11, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 d

  5. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    bind fixed in 9.14.12-r0; bind fixed in 9.14.12-r0; bind fixed in 9.14.12-r0; bind fixed in 9.14.12-r0

  6. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    bind fixed in 9.14.12-r0

  7. Oct 26, 2026 · Trivy Vulnerability DB

    Updated

    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 d

Sources

  • CVE.orgVulnerability recordCVE-2020-8617

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2020-8617

    30-day exploitation probability 93.33%

    first.org
  • Exploit DatabasePublic exploit reference48521

    Public exploit archive reference. This is not confirmation of exploitation. The exploit body is not stored here.

    exploit-db.com
  • Metasploit ModulesPublic exploit moduleauxiliary_dos/dns/bind_tsig_badtime

    Public module reference (normal). Module source is not copied into this catalog.

    rapid7.com
  • OpenSSF OSV / OSV ScannerPackage advisoryDEBIAN-CVE-2020-8617
    osv.dev
  • Trivy Vulnerability DBPackage advisoryALPINE-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 whos

    osv.dev

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.

  • FIRST EPSSNov 6, 2026
  • Metasploit ModulesNov 6, 2026
  • Exploit DatabaseOct 27, 2026
  • CVE.orgOct 26, 2026
  • Trivy Vulnerability DBOct 26, 2026
  • OpenSSF OSV / OSV ScannerOct 26, 2026