{"vuid":"VU#953860","idnumber":"953860","name":"Microsoft Windows privilege escalation vulnerability","keywords":["Multiple","products","security vulnerabilities","microsoft","windows","acl","registry","services","subinacl","sc","ms06-june","MS06-011"],"overview":"Microsoft Windows access controls may be improperly configured potentially allowing a local attacker to gain elevated privileges on a vulnerable system.","clean_desc":"Microsoft Windows provides numerous, fine grained permissions and privileges to control access to Windows components, such as services, files, and registry entries. Recent research has uncovered  insecure configurations within user accounts and groups on Microsoft Windows systems. These configurations may allow local attackers to gain access to, and manipulate system resources. The researchers have developed a model that analyzes permissions to expose privilege escalation vulnerabilities. The research focused on three particular components of the Windows architecture: Services Windows services may be installed and configured with unnecessary privileges. This may allow a lesser privileged user to access and change the settings for a service that runs with greater privileges. Of particular concern are the following privileges: The SERVICE_CHANGE_CONFIG access right allows a user to change the a service's configuration. This includes the executable that services launches and the user account with which a service runs as. According to Microsoft,  \"Because this grants the caller the right to change the executable file that the system runs, it should be granted only to administrators.\" The SERVICE_ALL_ACCESS access right allows a user full control over a service. Files and Directories Any privileges that allow the contents of a file or a directory to be modified should be granted to only trusted users. The following access rights a of particular concern: The FILE_ALL_ACCESS access right allows a user to completely control a file, including read, write and execute privileges. The FILE_APPEND_DATA access right allows a user to add data to a file. The FILE_WRITE_DATA access right allows a user to write and rewrite data to a file. Registry Keys Users with KEY_SET_VALUE permissions can modify registry keys that specify executables, DLLs, and/or Globally Unique Identifiers (GUIDs). The WRITE_DAC access right provides the ability to modify the access control list for a resource. Users granted this right have the ability to change the way they, or other users, access a resource. This may allow attackers to grant themselves, or others arbitrary permissions over a resource. Note that these issues can affect all software that is developed for the Microsoft Windows platform. Known Windows services that have weak permissions include, but may not belimited to Microsoft SSDP Discovery service (SSDPSRV)\nNetBios over TCP/IP service (NetBT) \nSmart Card service (SCardSvr)\nUniversal Plug and Play Device Host service (upnphost)\nDNS Client service (Dnscache)\nDHCP Client service (Dhcp)","impact":"A local user with valid login credentials may be able gain elevated privileges on a vulnerable Windows system. We are aware of publicly available exploit code that claims to be a tool to identify vulnerable services. Installing and running this code may allow a remote attacker to gain access to a system.","resolution":"These issues are corrected in Service Pack 2 for Microsoft Windows XP and Service Pack 1 for Microsoft Windows Server 2003. In addition, Microsoft Security Advisory 914457 and Microsoft Security Bulletin MS06-011 contain numerous workarounds to mitigate these vulnerabilities.","workarounds":"","sysaffected":"","thanks":"These vulnerabilities were reported by Sudhakar Govindavajhala and Andrew W. Appel.","author":"This document was written by Jeff Gennari.","public":["http://www.microsoft.com/technet/security/advisory/914457.mspx","http://www.microsoft.com/technet/security/Bulletin/MS06-011.mspx","http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/file_security_and_access_rights.asp","http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_security_and_access_rights.asp","http://www.cs.princeton.edu/~sudhakar/papers/winval.pdf","http://support.microsoft.com/?id=914392"],"cveids":["CVE-2006-0023"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-11-07T18:54:56Z","publicdate":"2006-01-31T00:00:00Z","datefirstpublished":"2006-02-08T02:07:58Z","dateupdated":"2006-04-21T21:58:51Z","revision":69,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"10","cam_exploitation":"0","cam_internetinfrastructure":"5","cam_population":"15","cam_impact":"20","cam_easeofexploitation":"5","cam_attackeraccessrequired":"10","cam_scorecurrent":"4.21875","cam_scorecurrentwidelyknown":"7.03125","cam_scorecurrentwidelyknownexploited":"12.65625","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":4.21875,"vulnote":null}