{"edition": 1, "title": "Microsoft Windows DHCP Client Service Crafted Response Overflow", "bulletinFamily": "software", "published": "2006-07-11T14:49:06", "lastseen": "2017-04-28T13:20:23", "modified": "2006-07-11T14:49:06", "reporter": "Mariano Nu\u00f1ez Di Croce(mnunez@cybsec.com)", "viewCount": 1, "href": "https://vulners.com/osvdb/OSVDB:27151", "description": "## Vulnerability Description\nAn unspecified remote overflow exists in Windows. The DHCP client fails to validate unspecified input resulting in a buffer overflow. With a specially crafted DHCP response, an attacker can cause arbitrary code execution resulting in a loss of integrity.\n## Solution Description\nCurrently, there are no known workarounds or upgrades to correct this issue. However, Microsoft has released a patch to address this vulnerability.\n## Short Description\nAn unspecified remote overflow exists in Windows. The DHCP client fails to validate unspecified input resulting in a buffer overflow. With a specially crafted DHCP response, an attacker can cause arbitrary code execution resulting in a loss of integrity.\n## References:\nSecurity Tracker: 1016468\n[Secunia Advisory ID:21010](https://secuniaresearch.flexerasoftware.com/advisories/21010/)\nOther Advisory URL: http://www.cybsec.com/vuln/CYBSEC-Security_Pre-Advisory_Microsoft_Windows_DHCP_Client_Service_Remote_Buffer_Overflow.pdf\nNews Article: http://news.com.com/Attack+code+puts+Windows+PCs+at+risk/2100-7349_3-6098293.html\nMicrosoft Security Bulletin: MS06-036\nMicrosoft Knowledge Base Article: 914388\nMail List Post: http://archives.neohapsis.com/archives/fulldisclosure/2006-07/0222.html\nGeneric Exploit URL: http://www.milw0rm.com/exploits/2054\nFrSIRT Advisory: ADV-2006-2754\n[CVE-2006-2372](https://vulners.com/cve/CVE-2006-2372)\nCERT VU: 257164\nBugtraq ID: 18923\n", "affectedSoftware": [{"name": "Windows Server", "version": "2003 SP1", "operator": "eq"}, {"name": "Windows Server", "version": "2003 for Itanium", "operator": "eq"}, {"name": "Windows", "version": "XP SP2", "operator": "eq"}, {"name": "Windows", "version": "2000 SP4", "operator": "eq"}, {"name": "Windows", "version": "XP Professional x64 Edition", "operator": "eq"}, {"name": "Windows Server", "version": "2003", "operator": "eq"}, {"name": "Windows Server", "version": "2003 SP1 for Itanium", "operator": "eq"}, {"name": "Windows Server", "version": "2003 x64 Edition", "operator": "eq"}, {"name": "Windows", "version": "XP SP1", "operator": "eq"}], "type": "osvdb", "references": [], "enchantments": {"score": {"value": 8.0, "vector": "NONE", "modified": "2017-04-28T13:20:23", "rev": 2}, "dependencies": {"references": [{"type": "cve", "idList": ["CVE-2006-2372"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:13477"]}, {"type": "nessus", "idList": ["SMB_NT_MS06-036.NASL"]}, {"type": "cert", "idList": ["VU:257164"]}, {"type": "exploitdb", "idList": ["EDB-ID:2054"]}], "modified": "2017-04-28T13:20:23", "rev": 2}, "vulnersScore": 8.0}, "cvss": {"vector": "AV:NETWORK/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/", "score": 10.0}, "cvelist": ["CVE-2006-2372"], "id": "OSVDB:27151"}

{"cve": [{"lastseen": "2020-10-03T11:48:15", "description": "Buffer overflow in the DHCP Client service for Microsoft Windows 2000 SP4, Windows XP SP1 and SP2, and Server 2003 up to SP1 allows remote attackers to execute arbitrary code via a crafted DHCP response.", "edition": 3, "cvss3": {}, "published": "2006-07-11T21:05:00", "title": "CVE-2006-2372", "type": "cve", "cwe": ["CWE-119"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 10.0, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 10.0, "vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-2372"], "modified": "2018-10-18T16:39:00", "cpe": ["cpe:/a:microsoft:dhcp_client_service:*"], "id": "CVE-2006-2372", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2372", "cvss": {"score": 10.0, "vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:a:microsoft:dhcp_client_service:*:*:*:*:*:*:*:*"]}], "cert": [{"lastseen": "2020-09-18T20:43:14", "bulletinFamily": "info", "cvelist": ["CVE-2006-2372"], "description": "### Overview \n\nMicrosoft DHCP Client service contains a buffer overflow. This vulnerability may allow a remote attacker to execute arbitrary code on a vulnerable system. \n\n### Description \n\n**Dynamic Host Configuration Protocol (DHCP) **\n\nAs described in [RFC 2131](<http://www.faqs.org/rfcs/rfc2131.html>), \"The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network.\" \n \n**The Problem** \n \nThe Microsoft DHCP Client service contains a buffer overflow. If a remote attacker responds to a DHCP request with a specially crafted DHCP response, that attacker may be able to trigger the buffer overflow on the requesting system. \n \nFor more information refer to Microsoft Security Bulletin [MS06-036](<http://www.microsoft.com/technet/security/Bulletin/MS06-036.mspx>). \n \n--- \n \n### Impact \n\nA remote, unauthenticated attacker may be able to execute arbitrary code. \n \n--- \n \n### Solution \n\n**Apply a patch from your vendor **\n\nMicrosoft addresses this vulnerability with the updates listed in Microsoft Security Bulletin [](<http://www.microsoft.com/technet/security/Bulletin/MS06-039.mspx>)[MS06-036](<http://www.microsoft.com/technet/security/Bulletin/MS06-036.mspx>). \n \n--- \n \n### Vendor Information\n\n257164\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Additional information available\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n**Javascript is disabled. Click here to view vendors.**\n\n### Microsoft Corporation __ Affected\n\nUpdated: July 11, 2006 \n\n### Status\n\nAffected\n\n### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Vendor Information \n\nThe vendor has not provided us with any further information regarding this vulnerability.\n\n### Addendum\n\nRefer to <http://www.microsoft.com/technet/security/Bulletin/MS06-036.mspx>.\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23257164 Feedback>).\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | | \nTemporal | | \nEnvironmental | | \n \n \n\n\n### References \n\n * <http://www.microsoft.com/technet/security/bulletin/ms06-036.mspx>\n * <http://www.faqs.org/rfcs/rfc2131.html>\n\n### Acknowledgements\n\nThis vulnerability was reported in Microsoft Security Bulletin MS06-036. Microsoft credits Mariano Nu\u0f1ez Di Croce of Cybsec Security Systems for providing information regarding this vulnerability.\n\nThis document was written by Jeff Gennari.\n\n### Other Information\n\n**CVE IDs:** | [CVE-2006-2372](<http://web.nvd.nist.gov/vuln/detail/CVE-2006-2372>) \n---|--- \n**Severity Metric:** | 78.00 \n**Date Public:** | 2006-07-11 \n**Date First Published:** | 2006-07-11 \n**Date Last Updated: ** | 2006-07-13 21:21 UTC \n**Document Revision: ** | 11 \n", "modified": "2006-07-13T21:21:00", "published": "2006-07-11T00:00:00", "id": "VU:257164", "href": "https://www.kb.cert.org/vuls/id/257164", "type": "cert", "title": "Microsoft DHCP Client service contains a buffer overflow", "cvss": {"score": 10.0, "vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C"}}], "exploitdb": [{"lastseen": "2016-01-31T15:25:54", "description": "MS Windows DHCP Client Broadcast Attack Exploit (MS06-036). CVE-2006-2372. Remote exploit for windows platform", "published": "2006-07-21T00:00:00", "type": "exploitdb", "title": "Microsoft Windows - DHCP Client Broadcast Attack Exploit MS06-036", "bulletinFamily": "exploit", "cvelist": ["CVE-2006-2372"], "modified": "2006-07-21T00:00:00", "id": "EDB-ID:2054", "href": "https://www.exploit-db.com/exploits/2054/", "sourceData": "MS Windows DHCP Client Broadcast Attack Exploit (MS06-036)\r\n\r\nhttps://github.com/offensive-security/exploit-database-bin-sploits/raw/master/sploits/2054.tar.gz (07212006-MS06_036_DHCP_Client.tar.gz)\r\n\r\n# milw0rm.com [2006-07-21]\r\n", "cvss": {"score": 10.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "sourceHref": "https://www.exploit-db.com/download/2054/"}], "securityvulns": [{"lastseen": "2018-08-31T11:10:18", "bulletinFamily": "software", "cvelist": ["CVE-2006-2372"], "description": "Microsoft Security Bulletin MS06-036\r\nVulnerability in DHCP Client Service Could Allow Remote Code Execution &#40;914388&#41;\r\nPublished: July 11, 2006\r\n\r\nVersion: 1.0\r\nSummary\r\n\r\nWho Should Read this Document: Customers who use Microsoft Windows\r\n\r\nImpact of Vulnerability: Remote Code Execution\r\n\r\nMaximum Severity Rating: Critical\r\n\r\nRecommendation: Customers should apply the update immediately.\r\n\r\nSecurity Update Replacement: None\r\n\r\nCaveats: Microsoft Knowledge Base Article 914388 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 914388.\r\n\r\nTested Software and Security Update Download Locations:\r\n\r\nAffected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 2000 Service Pack 4 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Professional x64 Edition \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 x64 Edition \u2014 Download the update\r\n\r\nNon-Affected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 98, Microsoft Windows 98 Second Edition &#40;SE&#41;, and Microsoft Windows Millennium Edition &#40;Me&#41;\r\nTop of sectionTop of section\r\n\u2022\t\r\n\r\nThe software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site\r\n\r\nNote The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.\r\nGeneral Information\r\n\t\r\nExecutive Summary\r\n\r\nExecutive Summary:\r\n\r\nThis update resolves a newly discovered, privately reported vulnerability as well as additional issues discovered through internal investigations. The privately reported vulnerability is documented in the &quot;Vulnerability Details&quot; section of this bulletin.\r\n\r\nWe recommend that customers apply the update immediately\r\n\r\nSeverity Ratings and Vulnerability Identifiers:\r\nVulnerability Identifiers\tImpact of Vulnerability\tWindows 2000\tWindows XP Service Pack 1\tWindows XP Service Pack 2\tWindows Server 2003\tWindows Server 2003 Service Pack 1\r\n\r\nBuffer Overrun in DHCP Client Service Vulnerability - CVE-2006-2372\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\r\nAggregate Severity of All Vulnerabilities\r\n\t\r\n\r\n \r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\r\nThis assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.\r\n\r\nNote The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.\r\n\r\nNote The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:\r\n\u2022\t\r\n\r\nThe Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.\r\nTop of sectionTop of section\r\n\t\r\nFrequently Asked Questions &#40;FAQ&#41; Related to This Security Update\r\n\r\nAre Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?\r\nNo. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.\r\n\r\nExtended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?\r\n\r\nWindows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.\r\n\r\nCustomers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; to determine whether this update is required?\r\nThe following table provides the MBSA detection summary for this security update.\r\nSoftware\tMBSA 1.2.1\tMBSA 2.0\r\n\r\nMicrosoft Windows 2000 Service Pack 4\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 x64 Edition family\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nFor more information about MBSA, visit the MBSA Web site.\r\n\r\nFor more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660\r\n\r\nCan I use Systems Management Server &#40;SMS&#41; to determine whether this update is required?\r\nThe following table provides the SMS detection summary for this security update.\r\nSoftware\tSMS 2.0\tSMS 2003\r\n\r\nMicrosoft Windows 2000 Service Pack 4\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 x64 Edition family\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nSMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to software that MBSA does not detect.\r\n\r\nFor SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.\r\n\r\nFor SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.\r\n\r\nFor more information about SMS, visit the SMS Web site.\r\nTop of sectionTop of section\r\n\t\r\nVulnerability Details\r\n\t\r\nBuffer Overrun in DHCP Client Service Vulnerability - CVE-2006-2372\r\n\r\nThere is a remote code execution vulnerability in the DHCP Client service that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.\r\n\t\r\nMitigating Factors for Buffer Overrun in DHCP Client service Vulnerability - CVE-2006-2372:\r\n\u2022\t\r\n\r\nFor an attack to be successful the attacker must send the affected host a specially crafted DHCP response communication from the same network subnet.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Buffer Overrun in DHCP Client Service Vulnerability- CVE-2006-2372:\r\n\r\nMicrosoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\u2022\t\r\n\r\nUse a static IP address\r\n\r\nTo configure the system to use a static IP address follow these steps:\r\n\r\n1.\r\n\t\r\n\r\nObtain a static IP address from your network administrator\r\n\r\n2.\r\n\t\r\n\r\nClick Start, and then click Control Panel and then click Network and Internet Connections.\r\n\r\n3.\r\n\t\r\n\r\nRight-click the connection on which you want to specify to use a static IP address, and then click Properties.\r\n\r\n4.\r\n\t\r\n\r\nSelect Internet Protocol &#40;TCP/IP&#41; and click Properties.\r\n\r\n5.\r\n\t\r\n\r\nOn the General tab, click on the Use the following IP address and Use the following DNS server addresses radio buttons.\r\n\r\n6.\r\n\t\r\n\r\nInput your static IP address, subnet mask, default gateway, and DNS servers.\r\n\r\n7.\r\n\t\r\n\r\nClick Ok twice.\r\n\r\n8.\r\n\t\r\n\r\nRepeat steps 3 through 7 for each of your network adapters.\r\n\u2022\t\r\n\r\nDisable the DHCP Client service\r\n\r\nDisabling the DHCP Client service will help protect the affected system from attempts to exploit this vulnerability. To disable the DHCP Client service, follow these steps:\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Control Panel. Alternatively, point to Settings, and then click Control Panel.\r\n\r\n2.\r\n\t\r\n\r\nDouble-click Administrative Tools.\r\n\r\n3.\r\n\t\r\n\r\nDouble-click Services.\r\n\r\n4.\r\n\t\r\n\r\nDouble-click DHCP Client.\r\n\r\n5.\r\n\t\r\n\r\nIn the Startup type list, click Disabled.\r\n\r\n6.\r\n\t\r\n\r\nClick Stop, and then click OK.\r\n\r\nYou can also stop and disable the DHCP service by using the following command at the command prompt:\r\n\r\nsc stop DHCP &amp; sc config DHCP start= disabled\r\n\r\nImpact of Workaround: If you disable the DHCP service, you cannot automatically retrieve an IP address from a DHCP Server. Without an IP address you will not be able to connect to the network.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Buffer Overrun in DHCP Client Service Vulnerability - CVE-2006-2372:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a remote code execution vulnerability in the DHCP Client Service. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability?\r\nAn unchecked buffer in the DHCP Client service.\r\n\r\nWhat is DHCP?\r\nDynamic Host Configuration Protocol &#40;DHCP&#41; is an Internet Protocol standard that is designed to reduce the complexity of administering network addresses. DHCP does this by using a server computer to centrally manage IP addresses and other related configuration details used on your network. Windows Server provides the DHCP Server service, which enables the server computer to perform as a DHCP Server and to provide configuration settings to DHCP-enabled client computers using the DHCP Client service on your network as described in the DHCP IETF RFC 2131.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could take complete control of the affected system.\r\n\r\nWho could exploit the vulnerability?\r\nAn anonymous user could exploit the vulnerability by sending a malformed DHCP communication to an affected client on the same network segment. An attack is limited to a local subnet in a typical default network configuration scenario where DHCP or BOOTP forwarding is not enabled.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nAn attacker could exploit the vulnerability by answering a client\u2019s DHCP request on the local subnet with a specially crafted DHCP response.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nMicrosoft Windows 2000, Windows XP and Windows Server 2003 are primarily at risk from this vulnerability.\r\n\r\nAre Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?\r\nNo. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nAn attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by validating the way that the DHCP client handles DHCP related communications.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nNo. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nSecurity Update Information\r\n\r\nAffected Software:\r\n\r\nFor information about the specific security update for your affected software, click the appropriate link:\r\n\t\r\nWindows Server 2003 &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.\r\n\r\nNote The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting.\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstallation.\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log: path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program.\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting.\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003- kb914388-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB914388.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb914388-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.\r\n\r\nThis security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.\r\n\r\nRemoval Information\r\n\r\nTo remove this update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB914388$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n02:56\r\n\t\r\n\r\n104,448\r\n\t\r\n\r\nRTMGDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n02:56\r\n\t\r\n\r\n84,992\r\n\t\r\n\r\nRTMGDR\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n02:53\r\n\t\r\n\r\n104,448\r\n\t\r\n\r\nRTMQFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n02:53\r\n\t\r\n\r\n85,504\r\n\t\r\n\r\nRTMQFE\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n03:18\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nSP1GDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n03:18\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nSP1GDR\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n03:38\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nSP1QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n03:38\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nSP1QFE\r\n\r\nWindows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n287,232\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n229,888\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n104,448\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n84,992\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n287,232\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n230,400\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n104,448\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.536\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n85,504\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:22\r\n\t\r\n\r\n308,736\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:22\r\n\t\r\n\r\n261,632\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:22\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:22\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n308,736\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n261,632\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nWindows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n225,792\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1GDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n182,784\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n225,792\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n182,784\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows Server 2003&#92;SP2&#92;KB914388&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\t\r\nWindows XP &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in a future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting.\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstallation.\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program.\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting.\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:\r\n\r\nWindowsxp- kb914388-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB914388.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:\r\n\r\nWindowsxp- kb914388-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB914388$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\n6to4svc.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nSP1QFE\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n103,936\r\n\t\r\n\r\nSP1QFE\r\n\r\nDnsapi.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n140,288\r\n\t\r\n\r\nSP1QFE\r\n\r\nInetmib1.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n31,232\r\n\t\r\n\r\nSP1QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n83,456\r\n\t\r\n\r\nSP1QFE\r\n\r\nIpv6.exe\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n08:46\r\n\t\r\n\r\n48,640\r\n\t\r\n\r\nSP1QFE\r\n\r\nIpv6mon.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n54,272\r\n\t\r\n\r\nSP1QFE\r\n\r\nNetsh.exe\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n08:44\r\n\t\r\n\r\n83,456\r\n\t\r\n\r\nSP1QFE\r\n\r\nTcpip6.sys\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n08:46\r\n\t\r\n\r\n203,008\r\n\t\r\n\r\nSP1QFE\r\n\r\nTunmp.sys\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n08:44\r\n\t\r\n\r\n11,776\r\n\t\r\n\r\nSP1QFE\r\n\r\nWs2_32.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n70,656\r\n\t\r\n\r\nSP1QFE\r\n\r\nWship6.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:15\r\n\t\r\n\r\n13,312\r\n\t\r\n\r\nSP1QFE\r\n\r\nXpob2res.dll\r\n\t\r\n\r\n5.1.2600.1847\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n08:51\r\n\t\r\n\r\n159,232\r\n\t\r\n\r\nSP1QFE\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:59\r\n\t\r\n\r\n111,616\r\n\t\r\n\r\nSP2GDR\r\n\r\nDnsapi.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:59\r\n\t\r\n\r\n148,480\r\n\t\r\n\r\nSP2GDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n12:59\r\n\t\r\n\r\n94,720\r\n\t\r\n\r\nSP2GDR\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n13:46\r\n\t\r\n\r\n112,128\r\n\t\r\n\r\nSP2QFE\r\n\r\nDnsapi.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n13:46\r\n\t\r\n\r\n147,456\r\n\t\r\n\r\nSP2QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.1.2600.2912\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n13:46\r\n\t\r\n\r\n94,720\r\n\t\r\n\r\nSP2QFE\r\n\r\nWindows XP Professional x64:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n225,792\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1GDR\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n182,784\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:23\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n225,792\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1QFE\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n182,784\r\n\t\r\n\r\nx64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWdhcpcsvc.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n117,248\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nWiphlpapi.dll\r\n\t\r\n\r\n5.2.3790.2706\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n04:17\r\n\t\r\n\r\n95,232\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nFor Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP&#92;SP3&#92;KB914388&#92;Filelist\r\n\r\nFor Windows XP Professional x64 Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP Version 2003&#92;SP2&#92;KB911820&#92;Filelist\r\n\r\nNote These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\t\r\nWindows 2000 &#40;all versions&#41;\r\n\r\nPrerequisites\r\nFor Windows 2000, this security update requires Service Pack 4 &#40;SP4&#41;. For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a &#40;SP1a&#41; or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 &#40;SP4&#41;.\r\n\r\nThe software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nFor more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue may be included in a future Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting.\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstallation.\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program.\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting.\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nWindows2000- kb914388-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB914388.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nWindows2000- kb914388-x86-enu /norestart\r\n\r\nFor more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB914388$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options.\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed.\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nDisplays a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart.\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down.\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files.\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows 2000 Service Pack 4 and Small Business Server 2000:\r\nFile Name\tVersion\tDate\tTime\tSize\r\n\r\nDhcpcsvc.dll\r\n\t\r\n\r\n5.0.2195.7085\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n21:48\r\n\t\r\n\r\n89,872\r\n\r\nDnsapi.dll\r\n\t\r\n\r\n5.0.2195.7085\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n21:48\r\n\t\r\n\r\n136,976\r\n\r\nIphlpapi.dll\r\n\t\r\n\r\n5.0.2195.7097\r\n\t\r\n\r\n19-May-2006\r\n\t\r\n\r\n21:48\r\n\t\r\n\r\n68,368\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry key:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows 2000&#92;SP5&#92;KB914388&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the security update into the Windows installation source files.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\r\nAcknowledgments\r\n\r\nMicrosoft thanks the following for working with us to help protect customers:\r\n\u2022\t\r\n\r\nMariano Nu&#241;ez Di Croce of Cybsec Security Systems for reporting the Buffer Overrun in DHCP Client Service Vulnerability - CVE-2006-2372\r\n\r\nObtaining Other Security Updates:\r\n\r\nUpdates for other security issues are available at the following locations:\r\n\u2022\t\r\n\r\nSecurity updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for &quot;security_patch.&quot;\r\n\u2022\t\r\n\r\nUpdates for consumer platforms are available at the Microsoft Update Web site.\r\n\r\nSupport:\r\n\u2022\t\r\n\r\nCustomers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.\r\n\u2022\t\r\n\r\nInternational customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.\r\n\r\nSecurity Resources:\r\n\u2022\t\r\n\r\nThe Microsoft TechNet Security Web site provides additional information about security in Microsoft products.\r\n\u2022\t\r\n\r\nMicrosoft Software Update Services\r\n\u2022\t\r\n\r\nMicrosoft Windows Server Update Services\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer &#40;MBSA&#41;\r\n\u2022\t\r\n\r\nWindows Update\r\n\u2022\t\r\n\r\nMicrosoft Update\r\n\u2022\t\r\n\r\nWindows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.\r\n\u2022\t\r\n\r\nOffice Update \r\n\r\nSoftware Update Services:\r\n\r\nBy using Microsoft Software Update Services &#40;SUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.\r\n\r\nFor more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nWindows Server Update Services:\r\n\r\nBy using Windows Server Update Services &#40;WSUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.\r\n\r\nFor more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.\r\n\r\nSystems Management Server:\r\n\r\nMicrosoft Systems Management Server &#40;SMS&#41; delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.\r\n\r\nNote SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool &#40;available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack&#41; to install these updates.\r\n\r\nDisclaimer:\r\n\r\nThe information provided in the Microsoft Knowledge Base is provided &quot;as is&quot; without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.\r\n\r\nRevisions: \r\n\u2022\t\r\n\r\nV1.0 &#40;July 11, 2006&#41;: Bulletin published.", "edition": 1, "modified": "2006-07-11T00:00:00", "published": "2006-07-11T00:00:00", "id": "SECURITYVULNS:DOC:13477", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:13477", "title": "Microsoft Security Bulletin MS06-036 Vulnerability in DHCP Client Service Could Allow Remote Code Execution &#40;914388&#41;", "type": "securityvulns", "cvss": {"score": 10.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "nessus": [{"lastseen": "2021-01-01T05:43:23", "description": "The remote host contains a DHCP client that is vulnerable to a buffer\noverrun attack when receiving a malformed response to a DHCP request.\n\nAn attacker could exploit this flaw to execute arbitrary code on the\nremote host with 'SYSTEM' privileges.\n\nTypically, the attacker would need to be on the same physical subnet\nas this victim to exploit this flaw. Also, the victim needs to be\nconfigured to use DHCP.", "edition": 27, "published": "2006-07-11T00:00:00", "title": "MS06-036: Vulnerability in DHCP Client Service Could Allow Remote Code Execution (914388)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2006-2372"], "modified": "2021-01-02T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS06-036.NASL", "href": "https://www.tenable.com/plugins/nessus/22030", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(22030);\n script_version(\"1.35\");\n script_cvs_date(\"Date: 2018/11/15 20:50:30\");\n\n script_cve_id(\"CVE-2006-2372\");\n script_bugtraq_id(18923);\n script_xref(name:\"CERT\", value:\"257164\");\n script_xref(name:\"MSFT\", value:\"MS06-036\");\n script_xref(name:\"MSKB\", value:\"914388\");\n\n script_name(english:\"MS06-036: Vulnerability in DHCP Client Service Could Allow Remote Code Execution (914388)\");\n script_summary(english:\"Determines the presence of update 914388\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"Arbitrary code can be executed on the remote host due to a flaw in the\nDHCP client.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host contains a DHCP client that is vulnerable to a buffer\noverrun attack when receiving a malformed response to a DHCP request.\n\nAn attacker could exploit this flaw to execute arbitrary code on the\nremote host with 'SYSTEM' privileges.\n\nTypically, the attacker would need to be on the same physical subnet\nas this victim to exploit this flaw. Also, the victim needs to be\nconfigured to use DHCP.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2006/ms06-036\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP and\n2003.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_cwe_id(119);\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2006/07/11\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2006/07/11\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2006/07/11\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n\n script_copyright(english:\"This script is Copyright (C) 2006-2018 Tenable Network Security, Inc.\");\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_dependencies(\"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, 'Host/patch_management_checks');\n exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_func.inc\");\ninclude(\"misc_func.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS06-036';\nkb = '914388';\n\nkbs = make_list(kb);\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit(\"SMB/Registry/Enumerated\");\nget_kb_item_or_exit(\"SMB/WindowsVersion\", exit_code:1);\n\nif (hotfix_check_sp_range(win2k:'4,5', xp:'1,2', win2003:'0,1') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\nrootfile = hotfix_get_systemroot();\nif (!rootfile) exit(1, \"Failed to get the system root.\");\n\nshare = hotfix_path2share(path:rootfile);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif ( hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"Dhcpcsvc.dll\", version:\"5.2.3790.536\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.2\", sp:1, file:\"Dhcpcsvc.dll\", version:\"5.2.3790.2706\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:1, file:\"Dhcpcsvc.dll\", version:\"5.1.2600.1847\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:2, file:\"Dhcpcsvc.dll\", version:\"5.1.2600.2912\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.0\", file:\"Dhcpcsvc.dll\", version:\"5.0.2195.7085\", dir:\"\\system32\", bulletin:bulletin, kb:kb) )\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\n\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, 'affected');\n}\n", "cvss": {"score": 7.5, "vector": "AV:N/AC:L/Au:N/C:P/I:P/A:P"}}]}