We received the following advisory from ISC:
There was an error in the DNSSEC NSEC/NSEC3 validation code that could
cause bogus NXDOMAIN responses (that is, NXDOMAIN responses for records
proven by NSEC or NSEC3 to exist) to be cached as if they had validated
correctly, so that future queries to the resolver would return the bogus
NXDOMAIN with the AD flag set.
This problem affects all DNSSEC-validating resolvers. It would be
difficult to exploit due to other existing protections against cache
poisoning (including transaction ID and source port randomization), but
it could impair the ability of DNSSEC to protect against a
denial-of-service attack on a secure zone.
None, administrators need to upgrade to one of the versions detailed below.
None known at this time.
Upgrade BIND to one of the following: 9.4.3-P5, 9.5.2-P2 or 9.6.1-P3.
There are no fixes available for BIND versions 9.0 through 9.3, as those
releases are at End of Life. Note for BIND 9.7 beta-testers:
pre-releases of 9.7.0 are vulnerable. Upcoming releases will include
Created attachment 385125 [details]
Patch for CVE-2010-0097
This patch fixes CVE-2010-0097 (NSEC/NSEC3 validation code could cause bogus NXDOMAIN responses).
Created attachment 385126 [details]
Improved fix for CVE-2009-4022
Improved fix for CVE-2009-4022. This patch obsoletes original fix for CVE-2009-4022.
This is now public:
This issue has been addressed in following products:
Red Hat Enterprise Linux 5
Via RHSA-2010:0062 https://rhn.redhat.com/errata/RHSA-2010-0062.html
bind-9.6.1-9.P3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
bind-9.6.1-15.P3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.