CVE-2019-6475: A flaw in mirror zone validity checking can allow zone data to be spoofed
Cathy Almond
cathya at isc.org
Wed Oct 16 17:36:45 UTC 2019
CVE: CVE-2019-6475
Document version: 2.0
Posting date: 16 October 2019
Program impacted: BIND
Versions affected: BIND 9.14.0 -> 9.14.6. Also releases 9.15.0 ->
9.15.4 of the BIND 9.15 development branch.
Severity: Medium
Exploitable: Remotely
Description:
Mirror zones are a BIND feature allowing recursive servers to
pre-cache zone data provided by other servers. A mirror zone is
similar to a zone of type secondary, except that its data is
subject to DNSSEC validation before being used in answers, as
if it had been looked up via traditional recursion, and when
mirror zone data cannot be validated, BIND falls back to using
traditional recursion instead of the mirror zone. However, an
error in the validity checks for the incoming zone data can allow
an on-path attacker to replace zone data that was validated with
a configured trust anchor with forged data of the attacker's
choosing.
The mirror zone feature is most often used to serve a local copy
of the root zone. If an attacker was able to insert themselves
into the network path between a recursive server using a mirror
zone and a root name server, this vulnerability could then be
used to cause the recursive server to accept a copy of falsified
root zone data.
Impact:
An on-path attacker who manages to successfully exploit this
vulnerability can replace the mirrored zone (usually the root)
with data of their own choosing, effectively bypassing DNSSEC
protection.
CVSS Score: 5.9
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
For more information on the Common Vulnerability Scoring System and
to obtain your specific environmental score please visit:
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.
Workarounds:
The vulnerability can be avoided by not using mirror zones.
Active exploits:
None known.
Solution:
Upgrade to the patched release most closely related to your
current version of BIND:
+ BIND 9.14.7
+ BIND 9.15.5
Document revision history:
1.0 Early Notification, 09 October 2019
2.0 Public Disclosure, 16 October 2019
Related documents:
See our BIND 9 Security Vulnerability Matrix for a complete
listing of security vulnerabilities and versions affected.
Do you still have questions? Questions regarding this advisory
should go to security-officer at isc.org. To report a new issue, please
encrypt your message using security-officer at isc.org's PGP key which
can be found here:
https://www.isc.org/downloads/software-support-policy/openpgp-key/.
If you are unable to use encrypted email, you may also report new
issues at: https://www.isc.org/community/report-bug/.
Note:
ISC patches only currently supported versions. When possible we
indicate EOL versions affected. (For current information on which
versions are actively supported, please see
https://www.isc.org/downloads/.)
ISC Security Vulnerability Disclosure Policy:
Details of our current security advisory policy and practice can
be found in the ISC Software Defect and Security Vulnerability
Disclosure Policy.
Legal Disclaimer:
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.
More information about the bind-announce
mailing list