(acting as DNSSEC
validating resolver) could incorrectly mark zone data
as insecure when the zone being queried is undergoing a key algorithm
Posting date: 01 Dec 2010
9.0.x to 9.7.2-P2, 9.4-ESV to 9.4-ESV-R3, 9.6-ESV to 9.6-ESV-R2
named, acting as a DNSSEC validator, was
determining if an NS RRset is insecure based on a value that could mean
either that the RRset is actually insecure or that there wasn't a
matching key for the RRSIG in the DNSKEY RRset when resuming from
validating the DNSKEY RRset.
This can happen when in the middle of a
DNSKEY algorithm rollover, when two different algorithms were used to
sign a zone but only the new set of keys are in the zone DNSKEY RRset.
See http://tools.ietf.org/html/draft-ietf-dnsop-rfc4641bis-02#section-4.2.4 for example scenario.
Impact and Risk Assessment:
Answers are marked incorrectly as insecure.
CVSS Score: 5.0
CVSS Equation: (AV:N/AC:L/Au:N/C:N/I:P/A:N)
For more information on the Common Vulnerability Scoring System and to obtain your specific environmental score please visit: http://nvd.nist.gov/cvss.cfm?version=2&vector=(AV:N/AC:L/Au:N/C:N/I:P/A:N)
None known at this time.
If you are running anything not listed below, upgrade as other versions are EOL and not being patched.
9.4: upgrade to 9.4-ESV-R4, or newer
9.6: upgrade to 9.6.2-P3 or 9.6-ESV-R3, or newer
9.7: upgrade to 9.7.2-P3
Document Revision History:
Nov24-Corrected/updated: Versions Affected, CVSS Base Score and Solution
See our BIND Security Matrix for a complete listing of Security Vulnerabilities and versions affected.
If you'd like more information on our Forum or product support please visit www.isc.org/support.
Do you still have questions? Questions regarding this advisory should go to firstname.lastname@example.org
Note: ISC patches only currently supported versions. When possible we indicate EOL versions affected.
ISC Security Vulnerability Disclosure Policy: Details of our current security advisory policy and practice can be found here: https://www.isc.org/security-vulnerability-disclosure-policy
This Knowledge Base article https://kb.isc.org/article/AA-00936 is the complete and official security advisory document.
Internet Systems Consortium (ISC) is providing this notice on an "AS IS" basis. No warranty or guarantee of any kind is expressed in this notice and none should be implied. ISC expressly excludes and disclaims any warranties regarding this notice or materials referred to in this notice, including, without limitation, any implied warranty of merchantability, fitness for a particular purpose, absence of hidden defects, or of non-infringement. Your use or reliance on this notice or materials referred to in this notice is at your own risk. ISC may change this notice at any time. A stand-alone copy or paraphrase of the text of this document that omits the document URL is an uncontrolled copy. Uncontrolled copies may lack important information, be out of date, or contain factual errors.
© 2001-2015 Internet Systems ConsortiumPlease help us to improve the content of our knowledge base by letting us know below how we can improve this article. If you have a technical question or problem on which you'd like help, please don't submit it here as article feedback. For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership.ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.