RHSA-2010:0062: Moderate: bind security update

Published Jan 20, 2010
·
Updated

The Berkeley Internet Name Domain (BIND) is an implementation of the DomainName System (DNS) protocols. BIND includes a DNS server (named); a resolverlibrary (routines for applications to use when interfacing with DNS); andtools for verifying that the DNS server is operating correctly.A flaw was found in the BIND DNSSEC NSEC/NSEC3 validation code. If BIND wasrunning as a DNSSEC-validating resolver, it could incorrectly cacheNXDOMAIN responses, as if they were valid, for records proven by NSEC orNSEC3 to exist. A remote attacker could use this flaw to cause a BINDserver to return the bogus, cached NXDOMAIN responses for valid records andprevent users from retrieving those records (denial of service).(CVE-2010-0097)The original fix for CVE-2009-4022 was found to be incomplete. BIND wasincorrectly caching certain responses without performing proper DNSSECvalidation. CNAME and DNAME records could be cached, without proper DNSSECvalidation, when received from processing recursive client queries thatrequested DNSSEC records but indicated that checking should be disabled. Aremote attacker could use this flaw to bypass the DNSSEC validation checkand perform a cache poisoning attack if the target BIND server wasreceiving such client queries. (CVE-2010-0290)All BIND users are advised to upgrade to these updated packages, whichcontain a backported patch to resolve these issues. After installing theupdate, the BIND daemon (named) will be restarted automatically.

Affected Software

16 affected componentsFixes available
redhat/bind<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-chroot<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-devel<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-devel<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-libbind-devel<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-libbind-devel<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-libs<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-libs<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-sdb<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-utils<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/caching-nameserver<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-chroot<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-sdb<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/bind-utils<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2
redhat/caching-nameserver<9.3.6-4.P1.el5_4.2
9.3.6-4.P1.el5_4.2

Remediation

Event History

Jan 20, 2010
Advisory Published
via Red Hat·12:00 AM

Frequently Asked Questions

1

What is the severity of RHSA-2010:0062?

The severity of RHSA-2010:0062 is classified as moderate.

2

What vulnerabilities does RHSA-2010:0062 address?

RHSA-2010:0062 addresses vulnerabilities in the Berkeley Internet Name Domain (BIND) related to DNS protocol implementations.

3

How do I fix RHSA-2010:0062?

To fix RHSA-2010:0062, you should update BIND to version 9.3.6-4.P1.el5_4.2 or later.

4

Which packages are affected by RHSA-2010:0062?

Affected packages by RHSA-2010:0062 include bind, bind-utils, bind-devel, and several others.

5

Are there any special instructions for applying the fix for RHSA-2010:0062?

Yes, it's recommended to back up your configurations before applying the update for RHSA-2010:0062.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203