{"id": "SECURITYVULNS:VULN:6944", "bulletinFamily": "software", "title": "Microsoft Windows memory corruption", "description": "CSRSS memory corruption on MessageBox with MB_SERVICE_NOTIFICATION beginning with "\??\".", "published": "2007-04-11T00:00:00", "modified": "2007-04-11T00:00:00", "cvss": {"score": 7.2, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "href": "https://vulners.com/securityvulns/SECURITYVULNS:VULN:6944", "reporter": "WINS", "references": ["https://vulners.com/securityvulns/securityvulns:doc:15410", "https://vulners.com/securityvulns/securityvulns:doc:16645", "https://vulners.com/securityvulns/securityvulns:doc:15469", "https://vulners.com/securityvulns/securityvulns:doc:16646", "https://vulners.com/securityvulns/securityvulns:doc:15527"], "cvelist": ["CVE-2006-6696", "CVE-2007-1209", "CVE-2006-6797"], "type": "securityvulns", "lastseen": "2018-08-31T11:09:22", "edition": 1, "viewCount": 710, "enchantments": {"score": {"value": 6.1, "vector": "NONE"}, "dependencies": {"references": [{"type": "canvas", "idList": ["LOCALLPC"]}, {"type": "cert", "idList": ["VU:219848", "VU:740636"]}, {"type": "checkpoint_advisories", "idList": ["CPAI-2006-318"]}, {"type": "cve", "idList": ["CVE-2006-6696", "CVE-2006-6797", "CVE-2007-1209"]}, {"type": "nessus", "idList": ["SMB_NT_MS07-021.NASL"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310801719", "OPENVAS:801719"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:16645"]}]}, "backreferences": {"references": [{"type": "canvas", "idList": ["LOCALLPC"]}, {"type": "cert", "idList": ["VU:219848", "VU:740636"]}, {"type": "cve", "idList": ["CVE-2006-6696", "CVE-2006-6797", "CVE-2007-1209"]}, {"type": "nessus", "idList": ["SMB_NT_MS07-021.NASL"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:15410"]}]}, "exploitation": null, "vulnersScore": 6.1}, "affectedSoftware": [], "immutableFields": [], "cvss2": {}, "cvss3": {}, "_state": {"dependencies": 1647589307, "score": 0}}

{"nessus": [{"lastseen": "2021-08-19T13:14:07", "description": "The remote host is running a version of Windows containing a bug in the CSRSS error message handling routine that could allow an attacker to execute arbitrary code on the remote host by luring a user on the remote host into visiting a rogue website.\n\nAdditionally, the system is prone to the following types of attack :\n\n- Local Privilege Elevation\n\n- Denial of Service (Local)", "cvss3": {"score": null, "vector": null}, "published": "2007-04-10T00:00:00", "type": "nessus", "title": "MS07-021: Vulnerabilities in CSRSS Could Allow Remote Code Execution (930178)", "bulletinFamily": "scanner", "cvss2": {}, "cvelist": ["CVE-2006-6696", "CVE-2006-6797", "CVE-2007-1209"], "modified": "2018-11-15T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS07-021.NASL", "href": "https://www.tenable.com/plugins/nessus/25024", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(25024);\n script_version(\"1.31\");\n script_cvs_date(\"Date: 2018/11/15 20:50:30\");\n\n script_cve_id(\"CVE-2006-6696\", \"CVE-2006-6797\", \"CVE-2007-1209\");\n script_bugtraq_id(21688, 23324, 23338);\n script_xref(name:\"MSFT\", value:\"MS07-021\");\n script_xref(name:\"MSKB\", value:\"930178\");\n \n script_xref(name:\"CERT\", value:\"740636\");\n script_xref(name:\"CERT\", value:\"219848\");\n script_xref(name:\"EDB-ID\", value:\"2967\");\n\n script_name(english:\"MS07-021: Vulnerabilities in CSRSS Could Allow Remote Code Execution (930178)\");\n script_summary(english:\"Determines the presence of update 930178\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"Arbitrary code can be executed on the remote host through the web\nbrowser.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host is running a version of Windows containing a bug in the\nCSRSS error message handling routine that could allow an attacker to\nexecute arbitrary code on the remote host by luring a user on the remote\nhost into visiting a rogue website.\n\nAdditionally, the system is prone to the following types of attack :\n\n- Local Privilege Elevation\n\n- Denial of Service (Local)\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2007/ms07-021\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP, 2003 and\nVista.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:F/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:\"exploit_framework_canvas\", value:\"true\");\n script_set_attribute(attribute:\"canvas_package\", value:'CANVAS');\n script_cwe_id(119);\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2006/12/15\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2007/04/10\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2007/04/10\");\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) 2007-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\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 = 'MS07-021';\nkb = \"930178\";\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:'2', win2003:'0,2', vista:'0') <= 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 (\n hotfix_is_vulnerable(os:\"6.0\", sp:0, file:\"Winsrv.dll\", version:\"6.0.6000.16445\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"6.0\", sp:0, file:\"Winsrv.dll\", version:\"6.0.6000.20522\", min_version:\"6.0.6000.20000\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n\n hotfix_is_vulnerable(os:\"5.2\", sp:2, file:\"Winsrv.dll\", version:\"5.2.3790.4043\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.2\", sp:1, file:\"Winsrv.dll\", version:\"5.2.3790.2902\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"Winsrv.dll\", version:\"5.2.3790.658\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n\n hotfix_is_vulnerable(os:\"5.1\", file:\"Winsrv.dll\", version:\"5.1.2600.3103\", dir:\"\\System32\", bulletin:bulletin, kb:kb) ||\n\n hotfix_is_vulnerable(os:\"5.0\", file:\"Winsrv.dll\", version:\"5.0.2195.7135\", dir:\"\\System32\", bulletin:bulletin, kb:kb)\n)\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\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": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:21", "description": "Microsoft Security Bulletin MS07-021\r\nVulnerabilities in CSRSS Could Allow Remote Code Execution &#40;930178&#41;\r\nPublished: April 10, 2007\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\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 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems, Microsoft Windows Server 2003 with SP1 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nWindows Vista \u2014 Download the update\r\n\u2022\t\r\n\r\nWindows Vista x64 Edition \u2014 Download the update\r\n\r\nThe software in this list has been tested to determine whether the versions are affected. Other versions are either past their support life cycle or are not affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\nTop of sectionTop of section\r\nGeneral Information\r\n\t\r\nExecutive Summary\r\n\r\nExecutive Summary:\r\n\r\nThis update resolves several newly discovered, privately and publicly disclosed vulnerabilities. Each vulnerability is documented in its own subsection in the Vulnerability Details section of this bulletin.\r\n\r\nAn attacker who successfully exploited the most severe of these vulnerabilities could 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\nWe recommend that customers apply the update immediately.\r\n\r\nSeverity Ratings and Vulnerability Identifiers:\r\nVulnerability Identifiers\tImpact of Vulnerability\tWindows 2000 Professional Service Pack 4 \tWindows 2000 Server Service Pack 4 \tWindows XP Service Pack 2\tWindows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2\tWindows Vista\r\n\r\nMsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE-2006-6696\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\nCSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209\r\n\t\r\n\r\nElevation of Privilege\r\n\t\r\n\r\nNot Affected\r\n\t\r\n\r\nNot Affected\r\n\t\r\n\r\nNot Affected\r\n\t\r\n\r\nNot Affected\r\n\t\r\n\r\nImportant\r\n\r\nCSRSS DoS Vulnerability - CVE-2006-6797\r\n\t\r\n\r\nDenial of Service\r\n\t\r\n\r\nLow\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nLow\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nLow\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 severity ratings for non-x86 operating system versions map to the x86 operating system versions as follows:\r\n\u2022\t\r\n\r\nThe Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 severity rating is the same as the Windows XP Service Pack 2 severity rating.\r\n\u2022\t\r\n\r\nThe 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 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 Windows Server 2003 with SP2 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 2 severity rating.\r\n\u2022\t\r\n\r\nThe Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.\r\n\u2022\t\r\n\r\nThe Windows Server 2003 x64 Edition Service Pack 2 severity rating is the same as the Windows Server 2003 Service Pack 2 severity rating.\r\n\u2022\t\r\n\r\nThe Windows Vista x64 Edition severity rating is the same as the Windows Vista 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\nWhy does this update address several reported security vulnerabilities?\r\nThis update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.\r\n\r\nI am using an older version of the software discussed in this security bulletin; what should I do? \r\nThe supported software called out under in this bulletin has been tested to determine whether the versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nIt should be a priority for customers who have older versions of the software 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 older software 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\nProduct\tMBSA 1.2.1\tMBSA 2.0.1\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 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 Service Pack 1, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2\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, Microsoft Windows Server 2003 with SP1 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP2 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 and Microsoft Windows Server 2003 x64 Edition Service Pack 2\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nWindows Vista\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nSee Note for Windows Vista below\r\n\r\nWindows Vista x64 Edition\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nSee Note for Windows Vista below\r\n\r\nFor more information about MBSA, visit the MBSA Web site. For 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\nNote for Windows Vista MBSA 2.0.1 is not supported on Windows Vista but supports remote scans of computers running Windows Vista. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer &#40;MBSA&#41; support for Windows Vista.\r\n\r\nFor more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.\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\nProduct\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 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2\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, Microsoft Windows Server 2003 with SP1 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP2 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 and Microsoft Windows Server 2003 x64 Edition Service Pack 2\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nSMS 2.0 and SMS 2003 Software Update Services &#40;SUS&#41; Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.\r\n\r\nFor SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool &#40;SUIT&#41;, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, 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 &#40;ITMU&#41; 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 ITMU, 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\n\r\nFor more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.\r\nTop of sectionTop of section\r\n\t\r\nVulnerability Details\r\n\t\r\nMsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE-2006-6696:\r\n\r\nA remote code execution vulnerability exists in the Windows Client/Server Run-time Subsystem &#40;CSRSS&#41; process because of the way that it handles error messages. An attacker could exploit the vulnerability by constructing a specially crafted application that could potentially allow remote code execution.\r\n\r\nAdditionally, if a user viewed a specially crafted Web site, an attacker who successfully exploited this vulnerability could take complete control of an affected system.\r\n\t\r\nMitigating Factors for MsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE-2006-6696:\r\n\u2022\t\r\n\r\nIn a local attack scenario an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.\r\n\u2022\t\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for MsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE-2006-6696:\r\n\r\nWe have not identified any workarounds for this vulnerability.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for MsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE- CVE-2006-6696:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a remote code execution vulnerability. 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\nThe vulnerability is caused by incorrect handling of error messages by the Windows Client/Server Run-time Subsystem &#40;CSRSS&#41;.\r\n\r\nWhat is the Client/Server Run-time Subsystem?\r\nCSRSS is the user-mode portion of the Win32 subsystem. CSRSS stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. CSRSS is responsible for console windows, creating and/or deleting threads.\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\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.\r\n\r\nThe vulnerability could also be exploited by a locally logged-on user by executing a specially crafted application.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThis vulnerability requires that either a user either be logged on locally and run a specially crafted application or that a user is logged on and visits a Web site for malicious action to occur.\r\n\r\nTherefore, any systems where Internet Explorer is used frequently or where multiple users have permissions to log on locally and run untrusted applications, such as workstations or terminal servers, are at the most risk from this vulnerability.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nYes. An 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 modifying the way that the Client/Server Run-time Subsystem processes error messages.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nYes. While the initial report was provided through responsible disclosure, the vulnerability was later disclosed publicly by another security researcher. It has been assigned Common Vulnerability and Exposure number CVE-2006-6696. It also has been named Vista Memory Corruption Zero-Day by the larger security community. This security bulletin addresses the publicly 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 seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.\r\n\r\nDoes applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability? \r\nThis security update addresses the vulnerability that potentially could be exploited by using the published proof of concept code. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2006-6696.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nCSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209:\r\n\r\nA privilege elevation vulnerability exists in the way that the Windows 32 Client/Server Run-time Subsystem &#40;CSRSS&#41; handles its connections during the startup and stopping of processes.\r\n\t\r\nMitigating Factors for CSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209:\r\n\r\nAn attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for CSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209:\r\n\r\nWe have not identified any workarounds for this vulnerability.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for CSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209:\r\n\r\nWhat is the scope of the vulnerability? \r\nThis is a privilege elevation vulnerability. An attacker who successfully exploited this vulnerability could 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. To attempt to exploit the vulnerability, an attacker must be able to log on locally to the system and run a program.\r\n\r\nWhat causes the vulnerability? \r\nThe vulnerability is caused by the incorrect marshaling of system resources by the Client/Server Run-time Subsystem.\r\n\r\nWhat is the Client/Server Run-time Subsystem? \r\nCSRSS is the user-mode portion of the Win32 subsystem. CSRSS stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. CSRSS is responsible for console windows, creating and/or deleting threads.\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\nWhat systems are primarily at risk from the vulnerability? \r\nSystems where multiple users have permissions to log on locally and run untrusted applications, are at the most risk from this vulnerability.\r\n\r\nCould the vulnerability be exploited over the Internet? \r\nNo. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by ensuring the memory resources utilized by the Client/Server Run-time Subsystem are freed appropriately after use.\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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nCSRSS DoS Vulnerability - CVE-2006-6797:\r\n\r\nA denial of service vulnerability exists in the Client/Server Run-time Subsystem &#40;CSRSS&#41; service because of the way it handles error messages. An attacker could exploit the vulnerability by running a specially crafted application causing the system to restart.\r\n\t\r\nMitigating Factors for CSRSS DoS Vulnerability - CVE-2006-6797:\r\n\r\nAn attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for CSRSS DoS Vulnerability - CVE-2006-6797:\r\n\r\nWe have not identified any workarounds for this vulnerability.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for CSRSS DoS Vulnerability - CVE-2006-6797:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate their user rights, but it could cause the affected system to stop accepting requests.\r\n\r\nWhat causes the vulnerability?\r\nThe vulnerability is caused by incorrect error handling by the CSRSS service.\r\n\r\nWhat is the Client/Server Run-time Subsystem?\r\nCSRSS is the user-mode portion of the Win32 subsystem &#40;with Win32.sys being the kernel-mode portion&#41;. CSRSS stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. CSRSS is responsible for console windows, creating and/or deleting threads.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could cause the affected system to stop responding.\r\n\r\nWho could exploit the vulnerability?\r\nTo try to exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nTo exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and cause the system to stop responding and restart.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nWindows systems where multiple users have permissions to log on locally and run untrusted applications are at the most risk from this vulnerability.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nNo. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by ensuring that the Client/Server Run-time Subsystem correctly processes error messages.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.\r\n\r\nDoes applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability? \r\nThis security update addresses the vulnerability that potentially could be exploited by using the published proof of concept code. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2006-6797.\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 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\nThere are no more service packs planned for this operating system. The 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-kb930178-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 KB930178.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-kb930178-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\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;$NTUninstallKB930178$&#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\tFolder\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.0.2195.7135\r\n\t\r\n\r\n13-Mar-2007\r\n\t\r\n\r\n09:44\r\n\t\r\n\r\n245,520\r\n\t\r\n\r\n \r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.0.2195.7135\r\n\t\r\n\r\n13-Mar-2007\r\n\t\r\n\r\n09:44\r\n\t\r\n\r\n245,520\r\n\t\r\n\r\nuniproc\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 may be able to use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. See the frequently asked question, \u201cCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; to determine whether this update is required?\u201d in the section, Frequently Asked Questions &#40;FAQ&#41; Related to This Security Update, earlier in this bulletin.\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;KB930178&#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\n\t\r\nWindows XP &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Windows XP Service Pack 2 or Windows XP Professional x64 Edition. For more information on how to obtain the latest Windows XP service pack, see Microsoft Knowledge Base Article 322389. For more information on how to how to obtain Service Pack 2 for Windows XP Professional, x64 Edition, see the Download Center.\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-kb930178-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 KB930178.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-kb930178-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.\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;$NTUninstallKB930178$&#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 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\nwinsrv.dll\r\n\t\r\n\r\n5.1.2600.3103\r\n\t\r\n\r\n17-Mar-2007\r\n\t\r\n\r\n14:30\r\n\t\r\n\r\n292,864\r\n\t\r\n\r\nSP2GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.1.2600.3103\r\n\t\r\n\r\n17-Mar-2007\r\n\t\r\n\r\n14:27\r\n\t\r\n\r\n292,864\r\n\t\r\n\r\nSP2QFE\r\n\r\nWindows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:01\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP1GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP1QFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:05\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP2GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:01\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP2QFE\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 may be able to use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. See the frequently asked question, \u201cCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; to determine whether this update is required?\u201d in the section, Frequently Asked Questions &#40;FAQ&#41; Related to This Security Update, earlier in this bulletin.\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 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;KB930178&#92;Filelist\r\n\r\nFor Windows XP Professional x64 Edition and Windows XP Professional x64 Service Pack 2:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP Version 2003&#92;SP3&#92;KB930178&#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 Server 2003 &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Windows Server 2003, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Server 2003 for Itanium-based Systems, Windows Server 2003 with SP1 for Itanium-based Systems, Windows Server 2003 with SP2 for Itanium-based Systems, Windows Server 2003 x64 Edition, or Windows Server 2003 x64 Edition Service Pack 2.\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-kb930178-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 KB930178.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-kb930178-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.\r\n\r\nThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.\r\n\r\nThis security update does not support HotPatching. For more information about HotPatching and how to deploy this security update as a HotPatch, see Microsoft Knowledge Base Article 897341.\r\n\r\nNote Not all security updates support HotPatching, and some security updates that support HotPatching might require that you restart the server after you install the security update. HotPatching is only supported if the files being replaced by the security update are General Distribution Release &#40;GDR&#41; files. HotPatching is not supported if you have previously installed a hotfix to update one of the files included in the security update. For more information about this behavior, see Microsoft Knowledge Base Article 897341 and Microsoft Knowledge Base Article 824994.\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;$NTUninstallKB930178$&#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, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2, Windows Server 2003, Web Edition with SP2; Windows Server 2003, Standard Edition with SP2; Windows Server 2003, Enterprise Edition with SP2; Windows Server 2003, Datacenter Edition with SP2;; Windows Server 2003 R2, Standard Edition with SP2; Windows Server 2003 R2, Datacenter Edition with SP2; Windows Server 2003 R2, Enterprise Edition with SP2; and Windows Small Business Server 2003 R2 with SP2:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.658\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n06:08\r\n\t\r\n\r\n298,496\r\n\t\r\n\r\nRTMGDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.658\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n04:45\r\n\t\r\n\r\n299,520\r\n\t\r\n\r\nRTMQFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n04:31\r\n\t\r\n\r\n299,520\r\n\t\r\n\r\nSP1GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n05:18\r\n\t\r\n\r\n299,520\r\n\t\r\n\r\nSP1QFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n05:20\r\n\t\r\n\r\n301,056\r\n\t\r\n\r\nSP2GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n05:15\r\n\t\r\n\r\n301,056\r\n\t\r\n\r\nSP2QFE\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; Windows Server 2003, Enterprise Edition with SP2 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP2 for Itanium-based Systems:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.658\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n771,072\r\n\t\r\n\r\nRTMGDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.658\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n772,608\r\n\t\r\n\r\nRTMQFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n818,688\r\n\t\r\n\r\nSP1GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:03\r\n\t\r\n\r\n818,688\r\n\t\r\n\r\nSP1QFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:05\r\n\t\r\n\r\n818,688\r\n\t\r\n\r\nSP2GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n818,688\r\n\t\r\n\r\nSP2QFE\r\n\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; Windows Server 2003 with SP2, Standard x64 Edition; Windows Server 2003 with SP2, Enterprise x64 Edition; and Windows Server 2003 with SP2, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition with SP2; Windows Server 2003 R2, Enterprise x64 Edition with SP2; and Windows Server 2003 R2, Datacenter x64 Edition with SP2:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:01\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP1GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.2902\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:02\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP1QFE\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:05\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP2GDR\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n5.2.3790.4043\r\n\t\r\n\r\n21-Mar-2007\r\n\t\r\n\r\n08:01\r\n\t\r\n\r\n512,512\r\n\t\r\n\r\nSP2QFE\r\n\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 may be able to use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. See the frequently asked question, \u201cCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; to determine whether this update is required?\u201d in the section, Frequently Asked Questions &#40;FAQ&#41; Related to This Security Update, earlier in this bulletin.\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, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; and Windows Small Business Server 2003 R2:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows Server 2003&#92;SP3&#92;KB930178&#92;Filelist\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 Small Business Server 2003 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; Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; Windows Server 2003 R2, Datacenter x64 Edition; Windows Server 2003, Enterprise Edition with SP2; Windows Server 2003, Datacenter Edition with SP2; and Windows Small Business Server 2003 R2 with SP2:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows Server 2003&#92;SP3&#92;KB930178&#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 Vista &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires a released version of Windows Vista.\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\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/?, /h, /help\r\n\t\r\n\r\nDisplays help on supported switches.\r\n\r\n/quiet\r\n\t\r\n\r\nSuppresses the display of status or error messages.\r\n\r\n/norestart\r\n\t\r\n\r\nWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.\r\n\r\nNote For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.\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 Vista:\r\n\r\nWindows6.0-KB930178-x86.msu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages including failure messages. Administrators should use one of the supported methods to verify the installation was successful. Administrators should also review the system event logs 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 Vista:\r\n\r\nWindows6.0-KB930178-x86.msu /quiet /norestart\r\n\r\nFor 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 update, click Control Panel, click Security, then under Windows Update, click View installed updates and select from the list of updates.\r\n\r\nFile Information\r\n\r\nThis 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 Vista Ultimate, Windows Vista Enterprise, Windows Vista Business, Windows Vista Home Premium, Windows Vista Home Basic, and Windows Vista Starter:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\ncsrsrv.dll\r\n\t\r\n\r\n6.0.5600.20522\r\n\t\r\n\r\n23-Feb-2007\r\n\t\r\n\r\n04:04\r\n\t\r\n\r\n49,664\r\n\t\r\n\r\nKB930178&#92;x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.0.5600.20522_none_fd89691b0427207d\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n6.0.5600.20522\r\n\t\r\n\r\n23-Feb-2007\r\n\t\r\n\r\n04:05\r\n\t\r\n\r\n348,672\r\n\t\r\n\r\nKB930178&#92;x86_microsoft-windows-winsrv_31bf3856ad364e35_6.0.5600.20522_none_ea80c8b7fb1eb45f\r\n\r\n\r\n64-bit editions of Windows Vista Ultimate, Windows Vista Enterprise, Windows Vista Business, Windows Vista Home Premium, Windows Vista Home Basic, and Windows Vista Starter:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\ncsrsrv.dll\r\n\t\r\n\r\n6.0.6000.16445\r\n\t\r\n\r\n24-Feb-2007\r\n\t\r\n\r\n04:33\r\n\t\r\n\r\n86,016\r\n\t\r\n\r\n \r\n\t\r\n\r\nWindows6.0-KB930178-x64&#92;amd64_microsoft-windows-csrsrv_31bf3856ad364e35_6.0.6000.16445_none_239951d960b07637\r\n\r\ncsrsrv.dll\r\n\t\r\n\r\n6.0.6000.20544\r\n\t\r\n\r\n24-Feb-2007\r\n\t\r\n\r\n04:16\r\n\t\r\n\r\n86,016\r\n\t\r\n\r\n \r\n\t\r\n\r\nWindows6.0-KB930178-x64&#92;amd64_microsoft-windows-csrsrv_31bf3856ad364e35_6.0.6000.20544_none_2421ee5a79cefcaa\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n6.0.6000.16445\r\n\t\r\n\r\n24-Feb-2007\r\n\t\r\n\r\n04:36\r\n\t\r\n\r\n432,128\r\n\t\r\n\r\n \r\n\t\r\n\r\nWindows6.0-KB930178-x64&#92;amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.0.6000.16445_none_1090b17657a80a19\r\n\r\nwinsrv.dll\r\n\t\r\n\r\n6.0.6000.20544\r\n\t\r\n\r\n24-Feb-2007\r\n\t\r\n\r\n04:19\r\n\t\r\n\r\n432,128\r\n\t\r\n\r\n \r\n\t\r\n\r\nWindows6.0-KB930178-x64&#92;amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.0.6000.20544_none_11194df770c6908c\r\n\r\nNote When you install this security update, Windows checks to see if one or more of the files that are being updated on your system have previously been updated by a Windows hotfix. If you have previously installed a hotfix to update one of these files, the installer will apply the LDR version of this update. Otherwise, the installer will apply the GDR version of the update.\r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.\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 may be able to use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. See the frequently asked question, \u201cCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; to determine whether this update is required?\u201d in the section, Frequently Asked Questions &#40;FAQ&#41; Related to This Security Update, earlier in this bulletin.\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 enter an update file name in Start Search.\r\n\r\n2.\r\n\t\r\n\r\nWhen the file appears under Programs, right-click on the file name and click Properties.\r\n\r\n3.\r\n\t\r\n\r\nUnder the General tab, compare the file size with the file information tables provided earlier in this section.\r\n\r\n4.\r\n\t\r\n\r\nYou may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided earlier in this section.\r\n\r\n5.\r\n\t\r\n\r\nOn the Details 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\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\nTim Garnett of Determina Security Research for reporting the MsgBox &#40;CSRSS&#41; Remote Code Execution Vulnerability - CVE-2006-6696\r\n\u2022\t\r\n\r\neEye for reporting the CSRSS Local Elevation of Privilege Vulnerability - CVE-2007-1209\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\nTechNet Update Management Center\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 Scan 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;April 10, 2007&#41;: Bulletin published.", "edition": 1, "cvss3": {}, "published": "2007-04-11T00:00:00", "title": "Microsoft Security Bulletin MS07-021 Vulnerabilities in CSRSS Could Allow Remote Code Execution &#40;930178&#41;", "type": "securityvulns", "bulletinFamily": "software", "cvss2": {}, "cvelist": ["CVE-2006-6696", "CVE-2007-1209", "CVE-2006-6797"], "modified": "2007-04-11T00:00:00", "id": "SECURITYVULNS:DOC:16645", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:16645", "cvss": {"score": 7.2, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "cve": [{"lastseen": "2022-03-23T17:31:20", "description": "The Client Server Run-Time Subsystem (CSRSS) in Microsoft Windows allows local users to cause a denial of service (crash) or read arbitrary memory from csrss.exe via crafted arguments to the NtRaiseHardError function with status 0x50000018, a different vulnerability than CVE-2006-6696.", "cvss3": {}, "published": "2006-12-28T15:28:00", "type": "cve", "title": "CVE-2006-6797", "cwe": ["NVD-CWE-Other"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "NONE", "baseScore": 6.6, "vectorString": "AV:L/AC:L/Au:N/C:C/I:N/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 9.2, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-6696", "CVE-2006-6797"], "modified": "2018-10-17T21:49:00", "cpe": ["cpe:/o:microsoft:windows_xp:*"], "id": "CVE-2006-6797", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-6797", "cvss": {"score": 6.6, "vector": "AV:L/AC:L/Au:N/C:C/I:N/A:C"}, "cpe23": ["cpe:2.3:o:microsoft:windows_xp:*:gold:*:*:*:*:*:*"]}, {"lastseen": "2022-03-23T17:24:20", "description": "Double free vulnerability in Microsoft Windows 2000, XP, 2003, and Vista allows local users to gain privileges by calling the MessageBox function with a MB_SERVICE_NOTIFICATION message with crafted data, which sends a HardError message to Client/Server Runtime Server Subsystem (CSRSS) process, which is not properly handled when invoking the UserHardError and GetHardErrorText functions in WINSRV.DLL.", "cvss3": {}, "published": "2006-12-22T02:28:00", "type": "cve", "title": "CVE-2006-6696", "cwe": ["CWE-119"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.4, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 6.9, "vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-6696"], "modified": "2019-04-30T14:27:00", "cpe": ["cpe:/o:microsoft:windows_2003_server:standard", "cpe:/o:microsoft:windows_vista:*", "cpe:/o:microsoft:windows_2003_server:datacenter_edition", "cpe:/o:microsoft:windows_xp:*", "cpe:/o:microsoft:windows_2003_server:sp1", "cpe:/o:microsoft:windows_2000:*", "cpe:/o:microsoft:windows_2003_server:enterprise_edition", "cpe:/o:microsoft:windows_2003_server:web"], "id": "CVE-2006-6696", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-6696", "cvss": {"score": 6.9, "vector": "AV:L/AC:M/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:o:microsoft:windows_2003_server:datacenter_edition:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_vista:*:*:december_ctp:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:datacenter_edition:sp1_beta_1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:enterprise_edition:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:datacenter_edition:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:tablet_pc:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp3:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp4:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_vista:*:beta:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:standard:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp2:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_vista:*:beta2:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:standard:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:web:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:web:sp1_beta_1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:home:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:web:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:standard:sp1_beta_1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:enterprise_edition:sp1_beta_1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_vista:*:beta1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:gold:professional:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:home:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:home:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:sp1:*:enterprise:*:*:*:*:*"]}, {"lastseen": "2022-03-23T11:51:16", "description": "Use-after-free vulnerability in the Client/Server Run-time Subsystem (CSRSS) in Microsoft Windows Vista does not properly handle connection resources when starting and stopping processes, which allows local users to gain privileges by opening and closing multiple ApiPort connections, which leaves a \"dangling pointer\" to a process data structure.", "cvss3": {}, "published": "2007-04-10T21:19:00", "type": "cve", "title": "CVE-2007-1209", "cwe": ["CWE-399"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2007-1209"], "modified": "2018-10-16T16:37:00", "cpe": ["cpe:/o:microsoft:windows_vista:*"], "id": "CVE-2007-1209", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-1209", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:o:microsoft:windows_vista:*:*:*:*:*:*:*:*"]}], "openvas": [{"lastseen": "2020-04-27T19:22:55", "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS07-021.", "cvss3": {}, "published": "2011-01-14T00:00:00", "type": "openvas", "title": "Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)", "bulletinFamily": "scanner", "cvss2": {}, "cvelist": ["CVE-2006-6696", "CVE-2007-1209"], "modified": "2020-04-23T00:00:00", "id": "OPENVAS:1361412562310801719", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310801719", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n#\n# Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)\n#\n# Authors:\n# Madhuri D <dmadhuri@secpod.com>\n#\n# Copyright:\n# Copyright (C) 2011 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.801719\");\n script_version(\"2020-04-23T08:43:39+0000\");\n script_tag(name:\"last_modification\", value:\"2020-04-23 08:43:39 +0000 (Thu, 23 Apr 2020)\");\n script_tag(name:\"creation_date\", value:\"2011-01-14 09:03:25 +0100 (Fri, 14 Jan 2011)\");\n script_cve_id(\"CVE-2006-6696\", \"CVE-2007-1209\");\n script_bugtraq_id(23338);\n script_tag(name:\"cvss_base\", value:\"7.2\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:L/Au:N/C:C/I:C/A:C\");\n script_name(\"Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)\");\n script_xref(name:\"URL\", value:\"http://securitytracker.com/alerts/2007/Apr/1017897.html\");\n script_xref(name:\"URL\", value:\"https://docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-021\");\n\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2011 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"secpod_reg_enum.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/registry_enumerated\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation allows remote attackers to execute arbitrary code with\n SYSTEM privileges by establishing and closing multiple connections to the\n subsystem's ApiPort.\");\n script_tag(name:\"affected\", value:\"- Microsoft Windows XP Service Pack 2 and prior\n\n - Microsoft Windows 2000 ervice Pack 4 and prior\n\n - Microsoft Windows 2K3 Service Pack 2 and prior\n\n - Microsoft Windows Vista\");\n script_tag(name:\"insight\", value:\"The flaw is due to\n\n - A double-free error in the Client/Server Run-time Subsystem (CSRSS) within\n 'WINSRV.DLL' when handling HardError messages.\n\n - Incorrect marshaling of system resources in the Client/Server Run-time\n Subsystem (CSRSS) when handling connections during the startup and stopping\n of processes.\");\n script_tag(name:\"solution\", value:\"The vendor has released updates. Please see the references for more information.\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"summary\", value:\"This host is missing a critical security update according to\n Microsoft Bulletin MS07-021.\");\n exit(0);\n}\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win2k:5, xp:3, win2003:3, winVista:3) <= 0){\n exit(0);\n}\n\nif(hotfix_missing(name:\"930178\") == 0){\n exit(0);\n}\n\nsysPath = registry_get_sz(key:\"SOFTWARE\\Microsoft\\COM3\\Setup\",\n item:\"Install Path\");\nif(sysPath)\n{\n sysVer = fetch_file_version(sysPath:sysPath, file_name:\"winsrv.dll\");\n if(sysVer)\n {\n if(hotfix_check_sp(win2k:5) > 0)\n {\n if(version_is_less(version:sysVer, test_version:\"5.0.2195.7135\")){\n report = report_fixed_ver(installed_version:sysVer, fixed_version:\"5.0.2195.7135\");\n security_message(port: 0, data: report);\n }\n }\n\n else if(hotfix_check_sp(xp:3) > 0)\n {\n SP = get_kb_item(\"SMB/WinXP/ServicePack\");\n if(\"Service Pack 2\" >< SP)\n {\n if(version_is_less(version:sysVer, test_version:\"5.1.2600.3103\")){\n report = report_fixed_ver(installed_version:sysVer, fixed_version:\"5.1.2600.3103\");\n security_message(port: 0, data: report);\n }\n exit(0);\n }\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n\n else if(hotfix_check_sp(win2003:3) > 0)\n {\n SP = get_kb_item(\"SMB/Win2003/ServicePack\");\n if(\"Service Pack 1\" >< SP)\n {\n if(version_is_less(version:sysVer, test_version:\"5.2.3790.2902\")){\n report = report_fixed_ver(installed_version:sysVer, fixed_version:\"5.2.3790.2902\");\n security_message(port: 0, data: report);\n }\n exit(0);\n }\n if(\"Service Pack 2\" >< SP)\n {\n if(version_is_less(version:sysVer, test_version:\"5.2.3790.4043\")){\n report = report_fixed_ver(installed_version:sysVer, fixed_version:\"5.2.3790.4043\");\n security_message(port: 0, data: report);\n }\n exit(0);\n }\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n }\n}\n\nsysPath = registry_get_sz(key:\"SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\",\n item:\"PathName\");\nif(!sysPath){\n exit(0);\n}\n\nsysVer = fetch_file_version(sysPath:sysPath, file_name:\"system32\\winsrv.dll\");\nif(!sysVer){\n exit(0);\n}\n\nif(hotfix_check_sp(winVista:3) > 0)\n{\n if(version_is_less(version:sysVer, test_version:\"6.0.6000.16445\")){\n report = report_fixed_ver(installed_version:sysVer, fixed_version:\"6.0.6000.16445\");\n security_message(port: 0, data: report);\n }\n exit(0);\n}\n", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2017-07-02T21:13:29", "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS07-021.", "cvss3": {}, "published": "2011-01-14T00:00:00", "type": "openvas", "title": "Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)", "bulletinFamily": "scanner", "cvss2": {}, "cvelist": ["CVE-2006-6696", "CVE-2007-1209"], "modified": "2017-02-20T00:00:00", "id": "OPENVAS:801719", "href": "http://plugins.openvas.org/nasl.php?oid=801719", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_ms07-021.nasl 5362 2017-02-20 12:46:39Z cfi $\n#\n# Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)\n#\n# Authors:\n# Madhuri D <dmadhuri@secpod.com>\n#\n# Copyright:\n# Copyright (c) 2011 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\ntag_impact = \"Successful exploitation allows remote attackers to execute arbitrary code with\n SYSTEM privileges by establishing and closing multiple connections to the\n subsystem's ApiPort.\n Impact Level: System/Application\";\ntag_affected = \"Microsoft Windows XP Service Pack 2 and prior.\n Microsoft Windows 2000 ervice Pack 4 and prior.\n Microsoft Windows 2K3 Service Pack 2 and prior.\n Microsoft Windows Vista\";\ntag_insight = \"The flaw is due to\n - A double-free error in the Client/Server Run-time Subsystem (CSRSS) within\n 'WINSRV.DLL' when handling HardError messages.\n - Incorrect marshaling of system resources in the Client/Server Run-time\n Subsystem (CSRSS) when handling connections during the startup and stopping\n of processes.\";\ntag_solution = \"Run Windows Update and update the listed hotfixes or download and\n update mentioned hotfixes in the advisory from the below link,\n http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx\";\ntag_summary = \"This host is missing a critical security update according to\n Microsoft Bulletin MS07-021.\";\n\nif(description)\n{\n script_id(801719);\n script_version(\"$Revision: 5362 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2017-02-20 13:46:39 +0100 (Mon, 20 Feb 2017) $\");\n script_tag(name:\"creation_date\", value:\"2011-01-14 09:03:25 +0100 (Fri, 14 Jan 2011)\");\n script_cve_id(\"CVE-2006-6696\", \"CVE-2007-1209\");\n script_bugtraq_id(23338);\n script_tag(name:\"cvss_base\", value:\"7.2\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:L/Au:N/C:C/I:C/A:C\");\n script_name(\"Microsoft Windows CSRSS CSRFinalizeContext Local Privilege Escalation Vulnerability (930178)\");\n script_xref(name : \"URL\" , value : \"http://secunia.com/advisories/23491/\");\n script_xref(name : \"URL\" , value : \"http://securitytracker.com/alerts/2007/Apr/1017897.html\");\n script_xref(name : \"URL\" , value : \"http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx\");\n \n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2011 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"secpod_reg_enum.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\n\n script_tag(name : \"impact\" , value : tag_impact);\n script_tag(name : \"affected\" , value : tag_affected);\n script_tag(name : \"insight\" , value : tag_insight);\n script_tag(name : \"solution\" , value : tag_solution);\n script_tag(name : \"summary\" , value : tag_summary);\n exit(0);\n}\n\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win2k:5, xp:3, win2003:3, winVista:3) <= 0){\n exit(0);\n}\n\n## Hotfix check\nif(hotfix_missing(name:\"930178\") == 0){\n exit(0);\n}\n\n## Get System32 path\nsysPath = registry_get_sz(key:\"SOFTWARE\\Microsoft\\COM3\\Setup\",\n item:\"Install Path\");\nif(sysPath)\n{\n sysVer = fetch_file_version(sysPath, file_name:\"winsrv.dll\");\n if(sysVer)\n {\n # Windows 2K\n if(hotfix_check_sp(win2k:5) > 0)\n {\n # Grep for winsrv.dll version < 5.0.2195.7135\n if(version_is_less(version:sysVer, test_version:\"5.0.2195.7135\")){\n security_message(0);\n }\n }\n \n ## Windows XP\n else if(hotfix_check_sp(xp:3) > 0)\n {\n SP = get_kb_item(\"SMB/WinXP/ServicePack\");\n if(\"Service Pack 2\" >< SP)\n {\n ## Grep for winsrv.dll version < 5.1.2600.3103\n if(version_is_less(version:sysVer, test_version:\"5.1.2600.3103\")){\n security_message(0);\n }\n exit(0);\n }\n security_message(0);\n }\n \n ## Windows 2003\n else if(hotfix_check_sp(win2003:3) > 0)\n {\n SP = get_kb_item(\"SMB/Win2003/ServicePack\");\n if(\"Service Pack 1\" >< SP)\n {\n ## Grep for winsrv.dll version < 5.2.3790.2902\n if(version_is_less(version:sysVer, test_version:\"5.2.3790.2902\")){\n security_message(0);\n }\n exit(0);\n }\n if(\"Service Pack 2\" >< SP)\n {\n ## Grep for winsrv.dll version < 5.2.3790.4043\n if(version_is_less(version:sysVer, test_version:\"5.2.3790.4043\")){\n security_message(0);\n }\n exit(0);\n }\n security_message(0);\n }\n }\n}\n\nsysPath = registry_get_sz(key:\"SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\",\n item:\"PathName\");\nif(!sysPath){\n exit(0);\n}\n\nsysVer = fetch_file_version(sysPath, file_name:\"system32\\winsrv.dll\");\nif(!sysVer){\n exit(0);\n}\n \n## Windows Vista\nif(hotfix_check_sp(winVista:3) > 0)\n{\n ## Grep for winsrv.dll version < 6.0.6000.16445\n if(version_is_less(version:sysVer, test_version:\"6.0.6000.16445\")){\n security_message(0);\n }\n exit(0);\n}\n", "cvss": {"score": 7.2, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "canvas": [{"lastseen": "2021-07-28T14:33:27", "description": "**Name**| localLPC \n---|--- \n**CVE**| CVE-2006-6696 \n**Exploit Pack**| [CANVAS](<http://http://www.immunityinc.com/products-canvas.shtml>) \n**Description**| LPC local (MS07-021) \n**Notes**| CVE Name: CVE-2006-6696 \nVENDOR: Microsoft \nMSADV: MS07-021 \nCVSS: 6.9 \nCVE Url: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6696 \nNotes: \nIf you get FFFFFFF that means inetinfo died (sorry), STATUS_PORT_CONNECTION_REFUSED is normal. Just keep trying. \nAlso note that this will try 100 times, you might want to use the halt functionality to stop it \nThere's a very small chance this exploit will cause a box to pop up for inetinfo \nSo run it from a spawned listener you don't mind using. \nDon't use this on a node spawned from inetinfo, or the node will die when inetinfo crashes \n \n\n", "edition": 4, "cvss3": {}, "published": "2006-12-22T02:28:00", "title": "Immunity Canvas: LOCALLPC", "type": "canvas", "bulletinFamily": "exploit", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.4, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 6.9, "vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-6696"], "modified": "2006-12-22T02:28:00", "id": "LOCALLPC", "href": "http://exploitlist.immunityinc.com/home/exploitpack/CANVAS/localLPC", "cvss": {"score": 6.9, "vector": "AV:L/AC:M/Au:N/C:C/I:C/A:C"}}], "checkpoint_advisories": [{"lastseen": "2021-12-17T12:38:14", "description": "The Microsoft Windows operating system is one of the most popular systems in use on workstations, home computers, and servers. The operating system is split into several subsystems one of which is the user space subsystem called the Client/Server Runtime Server Subsystem (CSRSS). The CSRSS contains support for console windows, creating and deleting threads, as well as some parts of the 16-bit virtual MS-DOS environment. The service is implemented by the csrss.exe binary executable which runs under user mode with System level privileges. There exists a memory corruption vulnerability in Microsoft Windows. The vulnerability is due to improper handling of \"HardError\" messages in Windows Client/Server Runtime Server Subsystem (CSRSS). A remote unauthenticated attacker can exploit this vulnerability by enticing the target user to visit a malicious website using Internet Explorer. Successful exploitation of this vulnerability may allow the remote attackers to execute arbitrary code with the privileges of the System. In an attack case where code injection is not successful, it results in a kernel error condition which is also known as the \"Blue Screen of Death\". The vulnerable system may reboot or halt which results in a denial of service condition. In a more sophisticated attack where code injection is successful, the behavior of the target is entirely dependent on the intended function of the injected code. The code in such a case would execute within the security context of the System level privileges.", "cvss3": {}, "published": "2010-03-23T00:00:00", "type": "checkpoint_advisories", "title": "Microsoft Windows CSRSS HardError Message Box (MS07-021; CVE-2006-6696)", "bulletinFamily": "info", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.4, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 6.9, "vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-6696"], "modified": "2010-03-23T00:00:00", "id": "CPAI-2006-318", "href": "", "cvss": {"score": 6.9, "vector": "AV:L/AC:M/Au:N/C:C/I:C/A:C"}}], "cert": [{"lastseen": "2021-09-28T17:51:43", "description": "### Overview\n\nThe Microsoft Windows Client/Server Run-time Subsystem (CSRSS) process fails to properly handle error messages. This vulnerability may allow a remote attacker to execute arbitrary code.\n\n### Description\n\nAccording to Microsoft Security Bulletin [MS07-021](<http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>):\n\n_CSRSS is the user-mode portion of the Win32 subsystem. CSRSS stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. CSRSS is responsible for console windows, creating and/or deleting threads._ \nThe CSRSS process fails to properly handle error messages possibly allowing a double free vulnerability to occur. \n \nMore information is available in Microsoft Security Bulletin [MS07-021](<http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>). \n \nNote that proof-of-concept code is available for this vulnerability. \n \n--- \n \n### Impact\n\nA remote attacker may be able to execute arbitrary code on a vulnerable system. \n \n--- \n \n### Solution\n\n**Apply update from Microsoft** \nMicrosoft has released an update for this vulnerability in Microsoft Security Bulletin [MS07-021](<http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>). \n \n--- \n \n### Vendor Information\n\n740636\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: April 10, 2007 \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/ms07-021.mspx>.\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23740636 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/ms07-021.mspx>\n * <http://www.determina.com/security.research/vulnerabilities/csrss-harderror.html>\n * <http://www.kuban.ru/forum_new/forum2/files/19124.html>\n * [http://bugtraq.ru/cgi-bin/forum.mcgi?type=sb&amp;b=21&amp;m=140672](<http://bugtraq.ru/cgi-bin/forum.mcgi?type=sb&b=21&m=140672>)\n * <http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>\n\n### Acknowledgements\n\nThis vulnerability was reported by Tim Garnett of Determina Security Research .\n\nThis document was written by Jeff Gennari.\n\n### Other Information\n\n**CVE IDs:** | [CVE-2006-6797](<http://web.nvd.nist.gov/vuln/detail/CVE-2006-6797>) \n---|--- \n**Severity Metric:** | 7.44 \n**Date Public:** | 2006-12-15 \n**Date First Published:** | 2007-04-10 \n**Date Last Updated: ** | 2007-04-11 10:50 UTC \n**Document Revision: ** | 14 \n", "cvss3": {}, "published": "2007-04-10T00:00:00", "type": "cert", "title": "Microsoft Windows CSRSS error handling vulnerability", "bulletinFamily": "info", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "NONE", "baseScore": 6.6, "vectorString": "AV:L/AC:L/Au:N/C:C/I:N/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 9.2, "obtainUserPrivilege": false}, "cvelist": ["CVE-2006-6797"], "modified": "2007-04-11T10:50:00", "id": "VU:740636", "href": "https://www.kb.cert.org/vuls/id/740636", "cvss": {"score": 6.6, "vector": "AV:L/AC:L/Au:N/C:C/I:N/A:C"}}, {"lastseen": "2021-09-28T17:51:43", "description": "### Overview\n\nThe Microsoft Windows Client/Server Run-time Subsystem (CSRSS) process fails to properly handle error messages. This vulnerability may allow an attacker to execute arbitrary code.\n\n### Description\n\nThe Microsoft Client/Server Run-time Subsystem (CSRSS) is an essential subsystem. CSRSS is responsible for console windows and creating and deleting threads.\n\nAccording to Microsoft Security Bulletin [MS07-021](<http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>): \n \n_A privilege elevation vulnerability exists in the way that the Windows 32 Client/Server Run-time Subsystem (CSRSS) handles its connections during the startup and stopping of processes._ \n \n--- \n \n### Impact\n\nA local authenticated attacker may be able to gain elevated privileges. \n \n--- \n \n### Solution\n\n**Apply update from Microsoft** \n \nMicrosoft has released an update for this vulnerability in Microsoft Security Bulletin [MS07-021](<http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx>). \n \n--- \n \n### Vendor Information\n\n219848\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: April 10, 2007 \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\nSee <http://www.microsoft.com/technet/security/bulletin/ms07-021.mspx> for more details.\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23219848 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/ms07-021.mspx>\n\n### Acknowledgements\n\nThanks to Microsoft for information that was used in this report. Microsoft credits eEye for reporting this vulnerability.\n\nThis document was written by Ryan Giobbi.\n\n### Other Information\n\n**CVE IDs:** | [CVE-2007-1209](<http://web.nvd.nist.gov/vuln/detail/CVE-2007-1209>) \n---|--- \n**Severity Metric:** | 0.08 \n**Date Public:** | 2007-04-10 \n**Date First Published:** | 2007-04-10 \n**Date Last Updated: ** | 2007-04-11 17:42 UTC \n**Document Revision: ** | 13 \n", "cvss3": {}, "published": "2007-04-10T00:00:00", "type": "cert", "title": "Microsoft Windows Vista CSRSS privilege escalation vulnerability", "bulletinFamily": "info", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": true, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2007-1209"], "modified": "2007-04-11T17:42:00", "id": "VU:219848", "href": "https://www.kb.cert.org/vuls/id/219848", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}]}