CVE-2020-8617
Publication date 19 May 2020
Last updated 24 July 2024
Ubuntu priority
Cvss 3 Severity Score
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.
Status
Package | Ubuntu Release | Status |
---|---|---|
bind9 | 20.04 LTS focal |
Fixed 1:9.16.1-0ubuntu2.1
|
18.04 LTS bionic |
Fixed 1:9.11.3+dfsg-1ubuntu1.12
|
|
16.04 LTS xenial |
Fixed 1:9.10.3.dfsg.P4-8ubuntu1.16
|
|
14.04 LTS trusty |
Fixed 1:9.9.5.dfsg-3ubuntu0.19+esm2
|
Get expanded security coverage with Ubuntu Pro
Reduce your average CVE exposure time from 98 days to 1 day with expanded CVE patching, ten-years security maintenance and optional support for the full stack of open-source applications. Free for personal use.
Get Ubuntu ProSeverity score breakdown
Parameter | Value |
---|---|
Base score | 5.9 · Medium |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
References
Related Ubuntu Security Notices (USN)
- USN-4365-1
- Bind vulnerabilities
- 19 May 2020
- USN-4365-2
- Bind vulnerabilities
- 20 May 2020