Please Install the Updated Packages.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named) a resolver library (routines for applications to use when interfacing with DNS) and tools for verifying that the DNS server is operating correctly. It was discovered that the bind packages created the &quot rndc.key&quot file with insecure file permissions. This allowed any local user to read the content of this file. A local user could use this flaw to control some aspects of the named daemon by using the rndc utility, for example, stopping the named daemon. This problem did not affect systems with the bind-chroot package installed. (CVE-2007-6283) A buffer overflow flaw was discovered in the &quot inet_network()&quot function, as implemented by libbind. An attacker could use this flaw to crash an application calling this function, with an argument provided from an untrusted source. (CVE-2008-0122) As well, these updated packages fix the following bugs: * when using an LDAP backend, missing function declarations caused segmentation faults, due to stripped pointers on machines where pointers are longer than integers. * starting named may have resulted in named crashing, due to a race condition during D-BUS connection initialization. This has been resolved in these updated packages. * the named init script returned incorrect error codes, causing the &quot status&quot command to return an incorrect status. In these updated packages, the named init script is Linux Standard Base (LSB) compliant. * in these updated packages, the &quot rndc [command] [zone]&quot command, where [command] is an rndc command, and [zone] is the specified zone, will find the [zone] if the zone is unique to all views. * the default named log rotation script did not work correctly when using the bind-chroot package. In these updated packages, installing bind-chroot creates the symbolic link &quot /var/log/named.log&quot , which points to &quot /var/named/chroot/var/log/named.log&quot , which resolves this issue. * a previous bind update incorrectly changed the permissions on the &quot /etc/openldap/schema/dnszone.schema&quot file to mode 640, instead of mode 644, which resulted in OpenLDAP not being able to start. In these updated packages, the permissions are correctly set to mode 644. * the &quot checkconfig&quot parameter was missing in the named usage report. For example, running the &quot service named&quot command did not return &quot checkconfi ... Description truncated, for more information please check the Reference URL

bind on Red Hat Enterprise Linux (v. 5 server)

• https://www.redhat.com/archives/rhsa-announce/2008-May/msg00020.html

---

Updated on 2015-03-25