CVE-2020-8617
high-risk
Published 2020-05-19
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.
Do I need to act?
!
92.6% chance of exploitation in next 30 days
EPSS score — higher than 7% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
!
1 public exploit available
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.5/10
High
NETWORK
/ LOW complexity
Affected Products (20)
Affected Vendors
References (24)
Third Party Advisory
http://packetstormsecurity.com/files/157836/BIND-TSIG-Denial-Of-Service.html
Third Party Advisory
https://security.netapp.com/advisory/ntap-20200522-0002/
Third Party Advisory
https://usn.ubuntu.com/4365-1/
Third Party Advisory
https://usn.ubuntu.com/4365-2/
Third Party Advisory
https://www.debian.org/security/2020/dsa-4689
Third Party Advisory
http://packetstormsecurity.com/files/157836/BIND-TSIG-Denial-Of-Service.html
and 4 more references
67
/ 100
high-risk
Severity
26/34 · High
Exploitability
20/34 · Moderate
Exposure
21/34 · High