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
Advisories
Source ID Title
Debian DLA Debian DLA DLA-2568-1 bind9 security update
Debian DSA Debian DSA DSA-4857-1 bind9 security update
EUVD EUVD EUVD-2020-29473 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
Ubuntu USN Ubuntu USN USN-4737-1 Bind vulnerability
Ubuntu USN Ubuntu USN USN-4737-2 Bind vulnerability
Fixes

Solution

Upgrade to the patched release most closely related to your current version of BIND: BIND 9.11.28 BIND 9.16.12 BIND Supported Preview Edition is a special feature-preview branch of BIND provided to eligible ISC support customers. BIND 9.11.28-S1 BIND 9.16.12-S1 Acknowledgments: ISC would like to thank an anonymous party, working in conjunction with Trend Micro Zero Day Initiative, for reporting this issue to us.


Workaround

This vulnerability only affects servers configured to use GSS-TSIG, most often to sign dynamic updates. If another mechanism can be used to authenticate updates, the vulnerability can be avoided by choosing not to enable the use of GSS-TSIG features. On some platforms it may be possible to build a working BIND installation that is not vulnerable to CVE-2020-8625 by providing the --disable-isc-spnego command-line argument when running the ./configure script in the top level of the BIND source directory, before compiling and linking named. Choosing to configure and build BIND without the ISC SPNEGO implementation does not produce a vulnerable BIND on any platform, but on platforms where GSSAPI support in the system is lacking, building without the ISC SPNEGO implementation may result in unusable GSSAPI features (such as an inability to use GSS-TSIG-signed DDNS updates).

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: isc

Published:

Updated: 2024-09-16T22:40:02.277Z

Reserved: 2020-02-05T00:00:00

Link: CVE-2020-8625

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2021-02-17T23:15:13.530

Modified: 2024-11-21T05:39:09.040

Link: CVE-2020-8625

cve-icon Redhat

Severity : Important

Publid Date: 2021-02-17T00:00:00Z

Links: CVE-2020-8625 - Bugzilla

cve-icon OpenCVE Enrichment

No data.