{"vuid":"VU#354648","idnumber":"354648","name":"Microsoft Windows NT 4.0/TSE Winsock2ProtocolCatalogMutex has insecure permissions (MS01-003)","keywords":["Microsoft","Windows NT","mutex","winsock","MS01-003","Winsock2ProtocolCatalogMutex"],"overview":"A mutex controlling access to resources required for networking on Windows NTMicrosoft Windows NT 4.0 and Microsoft Windows NT 4.0, Terminal Server Edition, has inappropriate permissions.","clean_desc":"In general terms, a  mutex is an object used to control access to a resource (e.g. a printer, disk, segment of memory, data structure, etc.) so that only a single \"consumer\" (e.g. a process or program) can have access to the resource at any one time. That is, it enforces a policy of mutual exclusion between would-be consumers of a resource, typically  so that access to the resource can by properly synchronized. A process that has acess to a resource controlled by a mutex is said to have locked the mutex. A process that \"wants\" a resource locked by another process is said to be waiting on the mutex, or waiting on a locked mutex. Microsoft Windows NT 4.0 and Microsoft Windows NT 4.0, Terminal Server Edition uses a mutex named Winsock2ProtocolCatalogMutex to control access to resources required for NT networking to function properly. On unpatched versions of Windows, the mutex is protected inappropriately  so that ordinary users can disable access to  the mutex by changing the ACL on the mutex , or lock the mutex indefinitely. In either case, the intruder can effectively disable network access on that machine.","impact":"Intruders who can log in locally can effectively disable network access for the machine.","resolution":"Apply a patch as described in  MS01-003.","workarounds":"","sysaffected":"","thanks":"Our thanks to Arne Vidstrom who discovered the problem, and Microsoft for the information provided in their bulletin.","author":"This document was written by Shawn V. Hernan.","public":["http://www.microsoft.com/technet/security/bulletin/ms01-003.asp","http://www.microsoft.com/technet/security/bulletin/fq01-003.asp","http://ntsecurity.nu/advisories/a15.shtml"],"cveids":["CVE-2001-0006"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2001-01-26T22:32:55Z","publicdate":"2001-01-24T00:00:00Z","datefirstpublished":"2001-02-06T05:15:22Z","dateupdated":"2001-02-06T05:16:17Z","revision":7,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"4","cam_population":"8","cam_impact":"3","cam_easeofexploitation":"20","cam_attackeraccessrequired":"10","cam_scorecurrent":"2.16","cam_scorecurrentwidelyknown":"2.16","cam_scorecurrentwidelyknownexploited":"3.96","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":2.16,"vulnote":null}