Release Date: | 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.
See more information about CVE-2020-8617 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
Base Score: | 7.5 | Base Metrics: | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Access Vector: | Network | Attack Complexity: | Low |
Privileges Required: | None | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | None |
Integrity Impact: | None | Availability Impact: | High |
Platform | Errata | Release Date |
Oracle Linux version 6 (bind) | ELSA-2020-2383 | 2020-06-03 |
Oracle Linux version 7 (bind) | ELSA-2020-2344 | 2020-06-01 |
Oracle Linux version 8 (bind) | ELSA-2020-2338 | 2020-06-04 |
Oracle VM version 3.3 (bind) | OVMSA-2020-0021 | 2020-06-05 |
Oracle VM version 3.4 (bind) | OVMSA-2020-0021 | 2020-06-05 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team