Important CentOS bind97 Update
|bind97-9.7.0-10.P2.el5_8.1.i386.rpm, bind97-9.7.0-10.P2.el5_8.1.src.rpm, bind97-9.7.0-10.P2.el5_8.1.x86_64.rpm, bind97-chroot-9.7.0-10.P2.el5_8.1.i386.rpm, bind97-chroot-9.7.0-10.P2.el5_8.1.x86_64.rpm, bind97-devel-9.7.0-10.P2.el5_8.1.i386.rpm, bind97-devel-9.7.0-10.P2.el5_8.1.x86_64.rpm, bind97-libs-9.7.0-10.P2.el5_8.1.i386.rpm, bind97-libs-9.7.0-10.P2.el5_8.1.x86_64.rpm, bind97-utils-9.7.0-10.P2.el5_8.1.i386.rpm, bind97-utils-9.7.0-10.P2.el5_8.1.x86_64.rpm|
Updated bind97 packages that fix two security issues are now available for
Red Hat Enterprise Linux 5.
The Red Hat Security Response Team 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.
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.
A flaw was found in the way BIND handled zero length resource data records.
A malicious owner of a DNS domain could use this flaw to create
specially-crafted DNS resource records that would cause a recursive
resolver or secondary server to crash or, possibly, disclose portions of
its memory. (CVE-2012-1667)
A flaw was found in the way BIND handled the updating of cached name server
(NS) resource records. A malicious owner of a DNS domain could use this
flaw to keep the domain resolvable by the BIND server even after the
delegation was removed from the parent DNS zone. With this update, BIND
limits the time-to-live of the replacement record to that of the
time-to-live of the record being replaced. (CVE-2012-1033)
Users of bind97 are advised to upgrade to these updated packages, which
correct these issues. After installing the update, the BIND daemon (named)
will be restarted automatically.
Please see https://www.redhat.com/footer/terms-of-use.html
Am I vulnerable?
The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.
Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.Sign up for monitoring
Affected package information