CVE-2020-8625
Publication date 17 February 2021
Last updated 24 July 2024
Ubuntu priority
Cvss 3 Severity Score
BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting valid values for the tkey-gssapi-keytab or tkey-gssapi-credentialconfiguration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. The most likely outcome of a successful exploitation of the vulnerability is a crash of the named process. However, remote code execution, while unproven, is theoretically possible. Affects: BIND 9.5.0 -> 9.11.27, 9.12.0 -> 9.16.11, and versions BIND 9.11.3-S1 -> 9.11.27-S1 and 9.16.8-S1 -> 9.16.11-S1 of BIND Supported Preview Edition. Also release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch
Status
Package | Ubuntu Release | Status |
---|---|---|
bind9 | ||
20.04 LTS focal |
Fixed 1:9.16.1-0ubuntu2.6
|
|
18.04 LTS bionic |
Fixed 1:9.11.3+dfsg-1ubuntu1.14
|
|
16.04 LTS xenial |
Fixed 1:9.10.3.dfsg.P4-8ubuntu1.18
|
|
14.04 LTS trusty |
Fixed 1:9.9.5.dfsg-3ubuntu0.19+esm4
|
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 | 8.1 · High |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
References
Related Ubuntu Security Notices (USN)
- USN-4737-1
- Bind vulnerability
- 18 February 2021
- USN-4737-2
- Bind vulnerability
- 1 March 2021