{"vuid":"VU#411059","idnumber":"411059","name":"Microsoft Windows Universal Plug and Play service (UPNP) fails to limit the data returned in response to a NOTIFY message","keywords":["Microsoft Windows","XP","ME","Universal Plug and Play","UPNP","DoS","denial of service","User Datagram Protocol","UDP","SSDP advertisement","port 1900/tcp","MS01-059"],"overview":"Microsoft Windows Universal Plug and Play (UPnP) is vulnerable to a denial-of-service attack that could negatively affect the performance of vulnerable machines.","clean_desc":"Universal Plug and Play (UPnP) is a system designed to allow network devices to operate together. One of the UPnP protocols is called the Simple Service Discovery Protocol (SSDP). When a UPnP device joins a network, it announces itself through an SSDP NOTIFY message. The SSDP NOTIFY message includes a reference to a network location from which configuration information about the device can be retrieved. Other UPnP devices on the network that are interested in the newly announced device will consult the location specified in the NOTIFY message. An intruder can specify a specific location that may, for example, provide an enless stream of data (e.g.,  an echo service). The Microsoft Windows UPnP service will allocate memory in response to the endless stream of data, thus consuming memory and processor time, resulting in potentially severe performance degredation. For more information, see http://www.eeye.com/html/Research/Advisories/AD20011220.html\nhttp://www.microsoft.com/technet/security/bulletin/MS01-059.asp This vulnerability was discovered by Eeye Digital Security.","impact":"An intruder can consume memory and processor time on vulnerable systems.","resolution":"Apply a patch as described in MS01-059.","workarounds":"","sysaffected":"","thanks":"Our thanks to Eeye Digital Security, who discovered the problem, and Microsoft for the information contained in their bulletins.","author":"This document was written by Shawn V Hernan.","public":["http://www.microsoft.com/technet/security/bulletin/MS01-059.asp","http://www.microsoft.com/Downloads/Release.asp?ReleaseID=34991","http://download.microsoft.com/download/winme/Update/22940/WinMe/EN-US/314757USAM.EXE","http://www.microsoft.com/Downloads/Release.asp?ReleaseID=34951","http://www.upnp.org/","http://www.upnp.org/download/upnp_vendor_implementation_guide_jan2001.htm","http://www.upnp.org/download/draft_cai_ssdp_v1_03.txt"],"cveids":["CVE-2001-0877"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2001-12-20T19:12:10Z","publicdate":"2001-12-20T00:00:00Z","datefirstpublished":"2001-12-20T23:35:57Z","dateupdated":"2001-12-21T04:55:31Z","revision":13,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"10","cam_population":"15","cam_impact":"3","cam_easeofexploitation":"15","cam_attackeraccessrequired":"12","cam_scorecurrent":"4.55625","cam_scorecurrentwidelyknown":"4.55625","cam_scorecurrentwidelyknownexploited":"7.59375","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.55625,"vulnote":null}