Skip to content
Sign in
CVE-2020-86177.5HighCWE-617

CVE-2020-8617: A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c

ISC · BIND9

Vendor fix available · Affected: ISC BIND9 · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

93.3%probability of exploitation in the next 30 days
99th percentile
050100

Higher than 99% of scored CVEs

7.5HighCVSS 3.1
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ISC · BIND99.0.0 -> 9.11.18, 9.12.0 -> 9.12.4-P2, 9.14.0 -> 9.14.11, 9…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
ISC
Published
May 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-8617 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in