CVE-2020-8625

mediumPriorität · beachten · 54EPSS 0.642 · 99. PerzentilDEEURUUS
grimoire priorityP1 · Urgent
Exploitable?
—
no known exploitation
Likely / severe?
64.2% (99th) EPSS
CVSS 6.8 · medium
Is it mine?
1,257 products
Prüfe deine Angriffsfläche
Who says so?
7 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · bewertet 2026-10-26

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

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

  • Behobenbind-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-32:9.11.4-26.P2.el8_1.4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-chroot-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-chroot-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-chroot-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-chroot-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-debugsource-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-license-32:9.11.4-26.P2.el8_1.4.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenpython3-bind-32:9.11.4-26.P2.el8_1.4.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0669
  • Behobenbind-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-32:9.11.20-5.el8_3.1.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-chroot-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-chroot-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-chroot-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-chroot-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-debugsource-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-license-32:9.11.20-5.el8_3.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-lite-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-lite-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-lite-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-lite-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-lite-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-chroot-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-chroot-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-chroot-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-chroot-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenpython3-bind-32:9.11.20-5.el8_3.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0670
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0671
  • Behobenbind-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-32:9.8.2-0.68.rc1.el6_10.10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-devel-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-devel-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-devel-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-devel-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-libs-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-libs-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-libs-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-libs-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-utils-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-utils-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-utils-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0672
  • Behobenbind-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-libs-lite-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-lite-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-pkcs11-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-sdb-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0691
  • Behobenbind-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-chroot-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-utils-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-chroot-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-utils-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0692
  • Behobenbind-32:9.9.4-50.el7_3.5.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-chroot-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-debuginfo-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-debuginfo-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-debuginfo-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-debuginfo-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-libs-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-libs-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-libs-lite-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-libs-lite-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-license-32:9.9.4-50.el7_3.5.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-lite-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-lite-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-libs-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-libs-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-pkcs11-utils-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-sdb-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-sdb-chroot-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-utils-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0693
  • Behobenbind-32:9.9.4-29.el7_2.10.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-chroot-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-debuginfo-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-debuginfo-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-debuginfo-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-debuginfo-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-libs-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-libs-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-libs-lite-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-libs-lite-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-license-32:9.9.4-29.el7_2.10.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-lite-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-lite-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-libs-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-libs-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-pkcs11-utils-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-sdb-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-sdb-chroot-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-utils-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0694
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.src as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.src as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-chroot-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-chroot-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-chroot-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-export-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-libs-lite-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-license-32:9.11.4-9.P2.el7_7.4.noarch as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-license-32:9.11.4-9.P2.el7_7.4.noarch as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-lite-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-utils-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-utils-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-utils-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0727
  • Behobenbind-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-32:9.11.13-6.el8_2.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-chroot-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-chroot-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-chroot-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-chroot-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-debugsource-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-license-32:9.11.13-6.el8_2.2.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-lite-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-lite-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-lite-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-lite-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-lite-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-chroot-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-chroot-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-chroot-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-chroot-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenbind-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • Behobenpython3-bind-32:9.11.13-6.el8_2.2.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2021:0922
  • BehobenSINEC INSsiemens_psirt

    Update to V1.0.1.1 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109806100/
  • BehobenSINEC INScisa_csaf_ot

    Update to V1.0.1.1 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109806100/
  • Workaroundbind-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el8_1.4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-26.P2.el8_1.4.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.4-26.P2.el8_1.4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundpython3-bind-32:9.11.4-26.P2.el8_1.4.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.20-5.el8_3.1.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.20-5.el8_3.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.20-5.el8_3.1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundpython3-bind-32:9.11.20-5.el8_3.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-26.P2.el7_9.4.noarch as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-26.P2.el7_9.4.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.8.2-0.68.rc1.el6_10.10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.8.2-0.68.rc1.el6_10.10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.8.2-0.68.rc1.el6_10.10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.8.2-0.68.rc1.el6_10.10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.8.2-0.68.rc1.el6_10.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.src as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-74.el7_6.6.noarch as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390 as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server Optional (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.ppc64le as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.s390x as a component of Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-74.el7_6.6.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.6)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.src as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-51.el7_4.5.noarch as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.i686 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-51.el7_4.5.ppc64le as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server E4S (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-51.el7_4.5.x86_64 as a component of Red Hat Enterprise Linux Server TUS (v. 7.4)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-50.el7_3.5.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-50.el7_3.5.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-50.el7_3.5.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-50.el7_3.5.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.3)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-29.el7_2.10.src as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.9.4-29.el7_2.10.noarch as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-29.el7_2.10.i686 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.9.4-29.el7_2.10.x86_64 as a component of Red Hat Enterprise Linux Server AUS (v. 7.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.src as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.src as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-9.P2.el7_7.4.noarch as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.4-9.P2.el7_7.4.noarch as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.i686 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.s390 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server Optional EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-9.P2.el7_7.4.ppc64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-9.P2.el7_7.4.ppc64le as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-9.P2.el7_7.4.s390x as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux ComputeNode EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.4-9.P2.el7_7.4.x86_64 as a component of Red Hat Enterprise Linux Server EUS (v. 7.7)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.13-6.el8_2.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-chroot-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-debugsource-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-export-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-libs-lite-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-license-32:9.11.13-6.el8_2.2.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-lite-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-devel-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-libs-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-pkcs11-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-chroot-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-sdb-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.i686 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundbind-utils-debuginfo-32:9.11.13-6.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

  • Workaroundpython3-bind-32:9.11.13-6.el8_2.2.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)redhat_csaf

    As per upstream: 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. 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.

02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

8.1
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 6.8–8.1

v2.06.8mediumAV:N/AC:M/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USAusnutzbarkeit 8.6 · Auswirkung 6.4
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USAusnutzbarkeit 2.2 · Auswirkung 5.9
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:Csecondary · CISA US
v3.17.3highAV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondary · FSTEC (BDU) RU
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · ENISA EU
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · security-officer@isc.orgAusnutzbarkeit 2.2 · Auswirkung 5.9
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:Csecondary · Siemens ProductCERT DE
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Hsecondary · CVSS-BT (t0sche)
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · Red Hat Product Security US
03

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

CWE-120USprimärCWE-119USCWE-119USCWE-120USCWE-120USCWE-120US
04

betroffene Produkte (1,257)

Betroffene Produkte und Versionsbereiche.

20 von 1,257 angezeigt
05

Advisories (13)

Hersteller- und Ökosystem-Meldungen dazu.

  • RHSA-2021:0669Red Hat Security Advisory: bind security update2021-03-01csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 8.1 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0670Red Hat Security Advisory: bind security update2021-03-01csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0671Red Hat Security Advisory: bind security update2021-03-01csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0672Red Hat Security Advisory: bind security update2021-03-01csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 6 Extended Lifecycle Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0691Red Hat Security Advisory: bind security update2021-03-03csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7.6 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0692Red Hat Security Advisory: bind security update2021-03-03csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7.4 Advanced Update Support, Red Hat Enterprise Linux 7.4 Telco Extended Update Support, and Red Hat Enterprise Linux 7.4 Update Services for SAP Solutions. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0693Red Hat Security Advisory: bind security update2021-03-03csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7.3 Advanced Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0694Red Hat Security Advisory: bind security update2021-03-03csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7.2 Advanced Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0727Red Hat Security Advisory: bind security update2021-03-04csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 7.7 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:0922Red Hat Security Advisory: bind security update2021-03-17csaf · redhat_csafUS

    An update for bind is now available for Red Hat Enterprise Linux 8.2 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • SSA-389290SSA-389290: Third-Party Component Vulnerabilities in SINEC INS2022-03-08csaf · siemens_psirtDE

    71 vulnerabilities in third-party components as Node.js, cURL, SQLite, CivetWeb and DNS(ISC BIND) could allow an attacker to interfere with the affected product in various ways. Siemens has released an update for SINEC INS and recommends to update to the latest versions.

  • WID-SEC-W-2023-0063Juniper Junos Space: Mehrere SchwachstellenDeutsch2022-01-12csaf · cert_bundDE

    Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Juniper Junos Space ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, beliebigen Code auszuführen und seine Privilegien zu erweitern.

  • ICSA-22-069-09Siemens SINEC INS2022-03-08icsa · cisa_csaf_otUS

    71 vulnerabilities in third-party components as Node.js, cURL, SQLite, CivetWeb and DNS(ISC BIND) could allow an attacker to interfere with the affected product in various ways. Siemens has released an update for SINEC INS and recommends to update to the latest versions.

06

auch bekannt als (4)

Weitere Namen und Kennungen dieser Entität.

07

quellen

Welche Quellen diesen Datensatz belegen und wann.

cnnvdenisa_euvdfstec_bducert_bundcisa_csaf_otredhat_csafsiemens_psirtNVDCVE.orgMITRE
veröffentlicht 2021-02-17geändert 2026-06-17
09

Referenzen (54)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan