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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
|
History
07 Nov 2023, 03:26
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2020-05-19 14:15
Updated : 2024-02-28 17:47
NVD link : CVE-2020-8617
Mitre link : CVE-2020-8617
CVE.ORG link : CVE-2020-8617
JSON object : View
Products Affected
canonical
- ubuntu_linux
debian
- debian_linux
fedoraproject
- fedora
opensuse
- leap
isc
- bind
CWE
CWE-617
Reachable Assertion