CVE-2017-3141: Windows service and uninstall paths are not quoted when
BIND is installed, allowing for unintended programs to be run with
Administrator permissions under some circumstances.

CVE:               CVE-2017-3141
Document Version:  2.0
Posting date:      14 Jun 2017
Program Impacted:  BIND
Versions affected: 9.2.6-P2->9.2.9, 9.3.2-P1->9.3.6, 9.4.0->9.8.8,
                   9.9.0->9.9.10, 9.10.0->9.10.5, 9.11.0->9.11.1,
                   9.9.3-S1->9.9.10-S1, 9.10.5-S1
Severity:          Critical
Exploitable:       Locally


    The BIND installer on Windows uses an unquoted service path which
    can enable a local user to achieve privilege escalation if the host
    file system permissions allow this.


    This vulnerability exists in the installer delivered with BIND for
    Windows and not within BIND itself.  Non-Windows builds and
    installations are unaffected.  A manual installation of BIND where
    the service path is quoted when added would not be at risk.

CVSS Score:   7.2
CVSS Vector:  CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

For more information on the Common Vulnerability Scoring System and to
obtain your specific environmental score please visit:


    BIND installations on Windows are not at risk if the host file
    permissions prevent creation of a binary in a location where the
    service executor would run it instead of named.exe.

Active exploits:

    No known active exploits but this generic weakness is already a
    well-known attack vector if user file access permissions do not
    adequately prevent the installation of malicious executables.


    Upgrade to the patched release most closely related to your current
    version of BIND.  These can all be downloaded from

    - BIND 9 version 9.9.10-P1
    - BIND 9 version 9.10.5-P1
    - BIND 9 version 9.11.1-P1

    BIND Supported Preview Edition is a special feature preview branch
    of BIND provided to eligible ISC support customers.

    - BIND 9 version 9.9.10-S2
    - BIND 9 version 9.10.5-S2


    ISC would like to thank John Page aka hyp3rlinx for reporting this

Document Revision History:

    1.0 Advance Notification 6 June 2017
    1.1 Added acknowledgement 7 June 2017
    2.0 Public Announcement 14 June 2017

Related Documents:

    See our BIND9 Security Vulnerability Matrix at for a complete listing of
    Security Vulnerabilities and versions affected.

    If you'd like more information on ISC Subscription Support and
    Advance Security Notifications, please visit

Do you still have questions?  Questions regarding this advisory should
go to  To report a new issue, please encrypt
your message using's PGP key which can be found
here:  If
you are unable to use encrypted email, you may also report new issues


    ISC patches only currently supported versions. When possible we
    indicate EOL versions affected.  (For current information on which
    versions are actively supported, please see

ISC Security Vulnerability Disclosure Policy:

    Details of our current security advisory policy and practice can be
    found here:

This Knowledge Base article is the
complete and official security advisory document.

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

(C) 2017 Internet Systems Consortium
bind-announce mailing list

Reply via email to