{"vuid":"VU#787252","idnumber":"787252","name":"Microsoft Windows domain-configured client Group Policy fails to authenticate servers","keywords":["microsoft","windows","group policy","universal naming convention","unc"],"overview":"Microsoft Windows domain-configured client Group Policy fails to authenticate servers over Universal Naming Convention (UNC) paths.","clean_desc":"Microsoft has released MS15-011, detailing a critical flaw in which Windows domain-configured client Group Policy fails to authenticate servers over Universal Naming Convention (UNC) paths. Upon connecting to a network, Group Policy runs logon scripts to receive and apply policy data from a domain controller. By joining an attacker-controlled network, the vulnerable system will execute attacker-provided scripts since the server is not required to authenticate itself. Because of the way that the Multiple UNC Provider (MUP) iterates through UNC providers to establish a connection to the domain controller, the vulnerability may be remotely exploitable when a UNC path is resolved over the Internet. For more detailed information, visit Microsoft's blog about hardening Group Policy and JAS's JASBUG Fact Sheet.","impact":"A remote, unauthenticated attacker may execute arbitrary code and completely compromise vulnerable systems.","resolution":"Apply an update and configure Group Policy settings In addition to applying an update, administrators need to configure additional Group Policy settings in order to protect against the vulnerability. Note that in addition to the unsupported Windows XP and 2000, Windows Server 2003 will not be receiving an update to address this vulnerability despite being a supported operating system. Furthermore, Microsoft has not identified any workarounds or mitigations, recommending that security-conscious users upgrade their operating systems.","workarounds":"","sysaffected":"Many versions of Microsoft Windows operating systems are co","thanks":"Microsoft credits Jeff Schmidt of JAS Global Advisors, Dr. Arnoldo Muller-Molina of simMachines, and the Internet Corporation for Assigned Names and Numbers (ICANN) with discovering this issue.","author":"This document was written by Joel Land.","public":["https://msdn.microsoft.com/en-us/library/gg465305.aspx","https://technet.microsoft.com/en-us/library/security/ms15-011","https://support.microsoft.com/kb/3000483","http://blogs.technet.com/b/srd/archive/2015/02/10/ms15-011-amp-ms15-014-hardening-group-policy.aspx","https://www.jasadvisors.com/about-jas/jasbug-security-vulnerability-fact-sheet/"],"cveids":["CVE-2015-0008"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2015-02-12T19:22:57Z","publicdate":"2015-02-13T00:00:00Z","datefirstpublished":"2015-02-13T15:07:38Z","dateupdated":"2015-02-13T15:13:12Z","revision":21,"vrda_d1_directreport":"0","vrda_d1_population":"4","vrda_d1_impact":"4","cam_widelyknown":"0","cam_exploitation":"0","cam_internetinfrastructure":"0","cam_population":"0","cam_impact":"0","cam_easeofexploitation":"0","cam_attackeraccessrequired":"0","cam_scorecurrent":"0","cam_scorecurrentwidelyknown":"0","cam_scorecurrentwidelyknownexploited":"0","ipprotocol":"","cvss_accessvector":"N","cvss_accesscomplexity":"L","cvss_authentication":null,"cvss_confidentialityimpact":"C","cvss_integrityimpact":"C","cvss_availabilityimpact":"C","cvss_exploitablity":null,"cvss_remediationlevel":"OF","cvss_reportconfidence":"C","cvss_collateraldamagepotential":"LM","cvss_targetdistribution":"H","cvss_securityrequirementscr":"ND","cvss_securityrequirementsir":"ND","cvss_securityrequirementsar":"ND","cvss_basescore":"10","cvss_basevector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","cvss_temporalscore":"7.8","cvss_environmentalscore":"8.477982556032","cvss_environmentalvector":"CDP:LM/TD:H/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}