Red Hat Security Advisory: bind97 security update
Updated bind97 packages that fix two security issues are now available for Red Hat Enterprise Linux 5. Red Hat Product Security has rated this update as having Important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
describes (2)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-1286US | high8.6 | — | ||
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature r… | ||||
| CVE-2016-1285US | medium6.8 | — | ||
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a… | ||||
references
External citations — patches, advisories, analysis.
remediations (111)
- Fixedbind97-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.src as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.src as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-chroot-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-devel-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-libs-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Fixedbind97-utils-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2016:0458 - Workaroundbind97-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-32:9.7.0-21.P2.el5_11.6.src as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-chroot-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-chroot-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-chroot-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-chroot-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-chroot-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-debuginfo-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-devel-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.s390 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-libs-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-utils-32:9.7.0-21.P2.el5_11.6.i386 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-utils-32:9.7.0-21.P2.el5_11.6.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-utils-32:9.7.0-21.P2.el5_11.6.ppc as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-utils-32:9.7.0-21.P2.el5_11.6.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
- Workaroundbind97-utils-32:9.7.0-21.P2.el5_11.6.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan