|
Microsoft Security Bulletin MS10-022 - ImportantVulnerability in VBScript Scripting Engine Could Allow Remote Code Execution (981169)Published: April 13, 2010 Version: 1.0 Executive Summary This security update resolves a publicly disclosed vulnerability in VBScript on Microsoft Windows that could allow remote code execution. This security update is rated Important for Microsoft Windows 2000, Windows XP, and Windows Server 2003. On Windows Server 2008, Windows Vista, Windows 7, and Windows Server 2008 R2, the vulnerable code is not exploitable, however, as the code is present, this update is provided as a defense-in-depth measure and has no severity rating. For more information, see the subsection, Affected and Non-Affected Software, in this section. The vulnerability could allow remote code execution if a malicious Web site displayed a specially crafted dialog box on a Web page and a user pressed the F1 key, causing the Windows Help System to be started with a Windows Help File provided by the attacker. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. The security update addresses the vulnerability by modifying the way that the VBScript engine processes help files in protected mode. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information. This security update addresses the vulnerability first described in Microsoft Security Advisory 981169. Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871. For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service. See also the section, Detection and Deployment Tools and Guidance, later in this bulletin. Known Issues. Microsoft Knowledge Base Article 981169 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. Affected and Non-Affected SoftwareThe following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle. Affected Software Microsoft Windows 2000 Service Pack 4 | VBScript 5.1[1]
(KB981350)
VBScript 5.6
(KB981350)
VBScript 5.7
(KB981349) | Remote Code Execution | Important | None | Windows XP Service Pack 2 | VBScript 5.6
(KB981350) | Remote Code Execution | Important | None | Windows XP Service Pack 2 and Windows XP Service Pack 3 | VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | Remote Code Execution | Important | None | Windows XP Professional x64 Edition Service Pack 2 | VBScript 5.6
(KB981350)
VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | Remote Code Execution | Important | None | Windows Server 2003 Service Pack 2 | VBScript 5.6
(KB981350)
VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | Remote Code Execution | Important | None | Windows Server 2003 x64 Edition Service Pack 2 | VBScript 5.6
(KB981350)
VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | Remote Code Execution | Important | None | Windows Server 2003 with SP2 for Itanium-based Systems | VBScript 5.6
(KB981350)
VBScript 5.7
(KB981349) | Remote Code Execution | Important | None | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | None | None[2] | None | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | None | None[2] | None | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** | VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | None | None[2] | None | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** | VBScript 5.7
(KB981349)
VBScript 5.8
(KB981332) | None | None[2] | None | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | VBScript 5.7
(KB981349) | None | None[2] | None | Windows 7 for 32-bit Systems | VBScript 5.8
(KB981332) | None | None[2] | None | Windows 7 for x64-based Systems | VBScript 5.8
(KB981332) | None | None[2] | None | Windows Server 2008 R2 for x64-based Systems** | VBScript 5.8
(KB981332) | None | None[2] | None | Windows Server 2008 R2 for Itanium-based Systems | VBScript 5.8
(KB981332) | None | None[2] | None |
**Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options. [1]This security update upgrades your installation of VBScript 5.1 to VBScript 5.6. [2]Severity ratings do not apply to this update because the vulnerability discussed in this bulletin does not affect this software. However, as a defense-in-depth measure to protect against any possible new vectors identified in the future, Microsoft recommends that customers of this software apply this security update. | Frequently Asked Questions (FAQ) Related to This Security Update |
What version of VBScript is installed on my system?
The version of VBScript on a system is determined by the highest version included in Internet Explorer, the Windows operating system, or Windows Scripting Host that is installed on the system, and may change if a newer version of Microsoft Internet Explorer, Windows Service Pack or Windows Scripting Host is installed. For more information, see the MSDN article, VBScript Version Information. To determine which version of VBScript is on your system, perform the following steps: 1. | Open Windows Explorer. | 2. | Navigate to the %systemroot%\system32 directory. | 3. | Right-click on vbscript.dll, select Properties, and then click the Details tab. |
The version number will be listed in the File Version field. For example, if your file version starts with 5.8, for example 5.8.7600.16385, VBScript 5.8 is installed on your system. I am using VBScript 5.1. Is my system affected?
Yes, security update KB981350 applies to your system and will upgrade your version of VBScript to VBScript 5.6. See Microsoft Knowledge Base Article 981350 for more information about this update. Note VBScript 5.1 is only present on new installations of Microsoft Windows 2000 Service Pack 4 that do not yet have Internet Explorer 6 installed. On such a system, installing the security update will upgrade your version of VBScript to VBScript 5.6. I am using Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. Why am I receiving this update?
The vulnerability exists in a Windows file, vbscript.dll, that is included in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. Microsoft has not identified any way to exploit this vulnerability on computers using these operating systems. As a defense-in-depth measure, this security update is made available to all customers using supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. If I applied workarounds provided in Advisory 981169, do I need to reverse them before applying this update?
If you applied workarounds provided in Microsoft Security Advisory 981169, you do not need to undo them before you install this update. If you wish to undo the workarounds, it is safe to do so after installing the update. The advisory uses the workarounds recommended in this bulletin. Please review the corresponding Impact of Workaround information to learn more about what happens if you keep the workaround in place. Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details. I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site. It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs. Customers 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 in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ. | Severity Ratings and Vulnerability Identifiers |
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the April bulletin summary. For more information, see Microsoft Exploitability Index. |
VBScript 5.1 on Microsoft Windows 2000 Service Pack 4[1] | Important
Remote Code Execution | Important | VBScript 5.6 on Microsoft Windows 2000 Service Pack 4 | Important
Remote Code Execution | Important | VBScript 5.6 on Windows XP Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.6 on Windows XP Professional x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.6 on Windows Server 2003 Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.6 on Windows Server 2003 x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.6 on Windows Server 2003 with SP2 for Itanium-based Systems | Important
Remote Code Execution | Important | VBScript 5.7 on Microsoft Windows 2000 Service Pack 4 | Important
Remote Code Execution | Important | VBScript 5.7 on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Important
Remote Code Execution | Important | VBScript 5.7 on Windows XP Professional x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.7 on Windows Server 2003 Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.7 on Windows Server 2003 x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.7 on Windows Server 2003 with SP2 for Itanium-based Systems | Important
Remote Code Execution | Important | VBScript 5.7 on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 3 | None[2] | None | VBScript 5.7 on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | None[2] | None | VBScript 5.7 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** | None[2] | None | VBScript 5.7 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** | None[2] | None | VBScript 5.8 on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Important
Remote Code Execution | Important | VBScript 5.8 on Windows XP Professional x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.8 on Windows Server 2003 Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.8 on Windows Server 2003 x64 Edition Service Pack 2 | Important
Remote Code Execution | Important | VBScript 5.8 on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 3 | None[2] | None | VBScript 5.8 on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | None[2] | None | VBScript 5.8 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** | None[2] | None | VBScript 5.8 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** | None[2] | None | VBScript 5.8 on Windows 7 for 32-bit Systems | None[2] | None | VBScript 5.8 on Windows 7 for x64-based Systems | None[2] | None | VBScript 5.8 on Windows Server 2008 R2 for x64-based Systems** | None[2] | None | VBScript 5.8 on Windows Server 2008 R2 for Itanium-based Systems | None[2] | None |
**Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options. [1]This security update replaces your installation of VBScript 5.1 with VBScript 5.6. [2]Severity ratings do not apply to this update because the vulnerability discussed in this bulletin does not affect this software. However, as a defense-in-depth measure to protect against any possible new vectors identified in the future, Microsoft recommends that customers of this software apply this security update. | VBScript Help Keypress Vulnerability - CVE-2010-0483 |
A remote code execution vulnerability exists in the way that VBScript interacts with Windows Help files when using Internet Explorer. If a malicious Web site displayed a specially crafted dialog box and a user pressed the F1 key, the Windows Help System would be started with a Windows Help File provided by the attacker. If a user is logged on with administrative user rights, 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. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. On systems running Windows Server 2003, Internet Explorer Enhanced Security Configuration is enabled by default, which helps to mitigate against this issue. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-0483. | Mitigating Factors for VBScript Help Keypress Vulnerability - CVE-2010-0483 |
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation: | • | This vulnerability cannot be exploited on Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. | | • | This vulnerability requires user interaction. The vulnerability could not be exploited without user interaction even if the user visited a malicious Web site. Instead, an attacker would need to convince a user to press the F1 key on the keyboard while the Web site displays a scripted dialog box. | | • | In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site. | | • | By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML e-mail messages in the Restricted sites zone, removing the risk of an attacker being able to use this vulnerability to execute malicious code. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario. Additionally, Outlook 2007 uses a different component to render HTML e-mail, removing the risk of this exploit. | | • | By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. | | • | An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights. |
| Workarounds for VBScript Help Keypress Vulnerability - CVE-2010-0483 |
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality: | • | Do not press the F1 key when prompted by a Web site Successful exploitation of this vulnerability requires that users assist the exploit by pressing the F1 key on their keyboard. Our analysis shows that if users do not press the F1 key on their keyboard, the vulnerability cannot be exploited. Consequently, malicious Web sites may attempt to convince users to press the F1 key. Such a Web site could invoke an endless loop of dialog boxes that tell the user to press the F1 key to end the loop, or offer information such as pricing information or help to be revealed through the F1 key. Users are advised to avoid pressing F1 presented by Web pages or other Internet content. If a dialog box appears repeatedly in an attempt to convince the user to press F1, users may log off the system or use Task Manager to terminate the Internet Explorer process. | | • | Restrict access to the Windows Help System Successful exploitation of this vulnerability requires that the Windows Help System is functioning. You can help protect against exploitation of this vulnerability if you modify the ACL on winhlp32.exe to be more restrictive on Windows 2000, Windows XP, and Windows Server 2003 by running the following command from an administrative command line: echo Y | cacls "%windir%\winhlp32.exe" /E /P everyone:N
Note You must be logged in as administrator or have administrative credentials to complete this workaround. Impact of workaround. The Windows Help System will be unavailable, and users may not be able to invoke the help function in applications. The attempt to open the Help function in applications may lead to an error message. How to undo the workaround. Run the following command from an administrative command line: echo Y | cacls "%windir%\winhlp32.exe" /E /P everyone
Note You must be logged in as administrator or have administrative credentials to undo this workaround. | | • | Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High. To raise the browsing security level in Internet Explorer, follow these steps: 1. | On the Internet Explorer Tools menu, click Internet Options. | 2. | In the Internet Options dialog box, click the Security tab, and then click the Internet icon. | 3. | Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High. |
Note If no slider is visible, click Default Level, and then move the slider to High. Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High. Impact of workaround. There are side effects to blocking ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone". Add sites that you trust to the Internet Explorer Trusted sites zone After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone. To do this, follow these steps: 1. | In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. | 2. | In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites. | 3. | If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box. | 4. | In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add. | 5. | Repeat these steps for each site that you want to add to the zone. | 6. | Click OK two times to accept the changes and return to Internet Explorer. |
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update. |
| • | Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps: 1. | In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. | 2. | Click Internet, and then click Custom Level. | 3. | Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. | 4. | Click Local intranet, and then click Custom Level. | 5. | Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. | 6. | Click OK two times to accept the changes and return to Internet Explorer. |
Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly. Impact of workaround. There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone". Add sites that you trust to the Internet Explorer Trusted sites zone After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone. To do this, follow these steps: 1. | In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. | 2. | In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites. | 3. | If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box. | 4. | In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add. | 5. | Repeat these steps for each site that you want to add to the zone. | 6. | Click OK two times to accept the changes and return to Internet Explorer. |
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update. |
| FAQ for VBScript Help Keypress Vulnerability - CVE-2010-0483 |
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. What causes the vulnerability?
The vulnerability exists in the way that VBScript interacts with Windows Help files when using Internet Explorer. While Windows Help Files are inherently unsafe files, the implementation of VBScript on affected systems allows an attacker to specify a Help file location when displaying a dialog box on a Web page. If a visitor pressed the F1 key while such a dialog box is being displayed, this specially crafted Help file could be loaded by the Windows Help System, allowing execution of arbitrary code in the security context of the currently logged-on user. What is VBScript?
VBScript (Visual Basic Script) is an interpreted, object-based scripting language that is often used to make Web sites more flexible or interactive. VBScript scripts can run only in the presence of an interpreter or host, such as Active Server Pages (ASP), Internet Explorer, or Windows Script Host. For more information, see the MSDN article VBScript Fundamentals. What are unsafe file types?
Microsoft uses the concept of "unsafe file types" to help better protect users from executable content that an attacker could embed in such files. For more information, see the whitepaper Understanding Executable Content in Microsoft Products, and Microsoft Knowledge Base Article 291369. What is the F1 key?
F1 is one of the 12 function keys (F1 – F12) on a regular keyboard, typically located in the top row of keys. Function keys allow users to reach certain functions in an application by pressing only a single key on the keyboard. In most applications, F1 would bring up the Help function and many users are familiar with instructions such as "Press F1 for help". What is defense-in-depth?
In information security, defense-in-depth refers to an approach in which multiple layers of defense are in place to help prevent attackers from compromising the security of a network or system. What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. How could an attacker exploit the vulnerability?
Successful exploitation of this vulnerability requires that an attacker convince a user to visit a specially crafted Web page that displays a dialog box, and then convince the user to press the F1 key on the keyboard while this dialog box is being displayed. What systems are primarily at risk from the vulnerability?
Client, workstation, or terminal server systems where Internet Explorer is used to browse Web pages are primarily at risk. I am running Internet Explorer on Windows Server 2003 or Windows Server 2008. Does this mitigate this vulnerability?
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration, which mitigates this vulnerability. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration. How does configuring the Internet zone security setting to High protect me from this vulnerability?
Setting the Internet zone security setting to High protects against this vulnerability by disabling Active Scripting, which is required in order to exploit this vulnerability. Why is this vulnerability not exploitable on Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2?
Windows Vista, Windows Server 2008, Windows7, and Windows Server 2008 R2 include architectural improvements in the way that Internet Explorer interacts with the Windows operating system and VBScript. This prevents exploitation of this vulnerability, even though the vulnerable code is present on those systems where users have installed the Windows Help System. What does the update do?
This security update addresses the vulnerability by modifying the way that the VBScript engine processes help files in protected mode on affected versions of the Windows operating systems. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, there is no known attack vector to exploit this vulnerability, but the update can be installed as a defense-in-depth measure. When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2010-0483. This vulnerability was described in Microsoft Security Advisory 981169. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued. | Detection and Deployment Tools and Guidance |
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ. Note Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions. Detection and Deployment Guidance Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747. Microsoft Baseline Security Analyzer Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer. The following table provides the MBSA detection summary for this security update. Microsoft Windows 2000 Service Pack 4 | Yes | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Windows XP Professional x64 Edition Service Pack 2 | Yes | Windows Server 2003 Service Pack 2 | Yes | Windows Server 2003 x64 Edition Service Pack 2 | Yes | Windows Server 2003 with SP2 for Itanium-based Systems | Yes | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Yes | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Yes | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | Windows 7 for 32-bit Systems | Yes | Windows 7 for x64-based Systems | Yes | Windows Server 2008 R2 for x64-based Systems | Yes | Windows Server 2008 R2 for Itanium-based Systems | Yes |
The latest version of MBSA has been released: Microsoft Baseline Security Analyzer 2.1.1. For more information, see Microsoft Baseline Security Analyzer 2.1. Windows Server Update Services By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Microsoft Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Systems Management Server The following table provides the SMS detection and deployment summary for this security update. Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes | Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes | Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | No | No | Yes | Yes | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | Yes | Yes | Windows 7 for 32-bit Systems | No | No | Yes | Yes | Windows 7 for x64-based Systems | No | No | Yes | Yes | Windows Server 2008 R2 for x64-based Systems | No | No | Yes | Yes | Windows Server 2008 R2 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0. For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) 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, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003. System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007. For more information about SMS, visit the SMS Web site. For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles. Update Compatibility Evaluator and Application Compatibility Toolkit Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit. The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment. | Security Update Deployment |
Affected Software For information about the specific security update for your affected software, click the appropriate link: | Windows 2000 (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup | Deployment | | Installing without user intervention | For VBScript 5.1 and VBScript 5.6 on Windows 2000:
Windows2000-KB981350-x86-enu /quiet | | For VBScript 5.7 on Windows 2000:
Windows2000-KB981349-x86-enu /quiet | Installing without restarting | For VBScript 5.1 and VBScript 5.6 on Windows 2000:
Windows2000-KB981350-x86-enu /norestart | | For VBScript 5.7 on Windows 2000:
Windows2000-KB981349-x86-enu /norestart | Update log file | For VBScript 5.1 and VBScript 5.6: KB981350.log | | For VBScript 5.7: KB981349.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable | Removal Information | For VBScript 5.1 and VBScript 5.6, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981350$\Spuninst folder | | For VBScript 5.7, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981349$\Spuninst folder | File Information | For VBScript 5.1 and VBScript 5.6, see Microsoft Knowledge Base Article 981350 | | For VBScript 5.7, see Microsoft Knowledge Base Article 981349 | Registry Key Verification | For VBScript 5.1 and VBScript 5.6: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB981350\Filelist | | For VBScript 5.7: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB981349\Filelist |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If 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. For more information about the 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed. | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /overwriteoem | Overwrites OEM files without prompting. | /nobackup | Does not back up files needed for uninstall. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. | /extract[:path] | Extracts files without starting the Setup program. | /ER | Enables extended error reporting. | /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note 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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed. | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. | 5. | On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note 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. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files. |
| Windows XP (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.6 on Windows XP Service Pack 2:
WindowsXP-KB981350-x86-enu /quiet | | For VBScript 5.7 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB981349-x86-enu /quiet | | For VBScript 5.8 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
IE8-WindowsXP-KB981332-x86-enu /quiet | | For VBScript 5.6 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981350-x64-enu /quiet | | For VBScript 5.7 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981349-x64-enu /quiet | | For VBScript 5.8 on Windows XP Professional x64 Edition Service Pack 2:
IE8-WindowsServer2003.WindowsXP-KB981332-x64-enu /quiet | Installing without restarting | For VBScript 5.6 on Windows XP Service Pack 2:
WindowsXP-KB981350-x86-enu /norestart | | For VBScript 5.7 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB981349-x86-enu /norestart | | For VBScript 5.8 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
IE8-WindowsXP-KB981332-x86-enu /norestart | | For VBScript 5.6 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981350-x64-enu /norestart | | For VBScript 5.7 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981349-x64-enu /norestart | | For VBScript 5.8 on Windows XP Professional x64 Edition Service Pack 2:
IE8-WindowsServer2003.WindowsXP-KB981332-x64-enu /norestart | Update log file | For VBScript 5.6: KB981350.log | | For VBScript 5.7: KB981349.log | | For VBScript 5.8: KB981332-IE8.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable | Removal Information | For VBScript 5.6, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981350$\Spuninst folder | | For VBScript 5.7, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981349$\Spuninst folder | | For VBScript 5.8, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\IE8Updates\KB981332-IE8\Spuninst folder | File Information | For VBScript 5.6, see Microsoft Knowledge Base Article 981350 | | For VBScript 5.7, see Microsoft Knowledge Base Article 981349 | | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | For VBScript 5.6 on Windows XP Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB981350\Filelist | | For VBScript 5.7 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB981349\Filelist | | For VBScript 5.8 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB981332-IE8\Filelist | | For VBScript 5.6 on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB981350\Filelist | | For VBScript 5.7 on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB981349\Filelist | | For VBScript 5.8 on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP0\KB981332-IE8\Filelist |
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update. Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If 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. For more information about the 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed. | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /overwriteoem | Overwrites OEM files without prompting. | /nobackup | Does not back up files needed for uninstall. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. | /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. | /extract[:path] | Extracts files without starting the Setup program. | /ER | Enables extended error reporting. | /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note 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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. | 5. | On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note 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. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files. |
| Windows Server 2003 (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.6 on Windows Server 2003 Service Pack 2:
WindowsServer2003-KB981350-x86-enu /quiet | | For VBScript 5.7 on Windows Server 2003 Service Pack 2:
WindowsServer2003-KB981349-x86-enu /quiet | | For VBScript 5.8 on Windows Server 2003 Service Pack 2:
IE8-WindowsServer2003-KB981332-x86-enu /quiet | | For VBScript 5.6 on Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981350-x64-enu /quiet | | For VBScript 5.7 on Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981349-x64-enu /quiet | | For VBScript 5.8 on Windows Server 2003 x64 Edition Service Pack 2:
IE8-WindowsServer2003.WindowsXP-KB981332-x64-enu /quiet | | For VBScript 5.6 on Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB981350-ia64-enu /quiet | | For VBScript 5.7 on Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB981349-ia64-enu /quiet | Installing without restarting | For VBScript 5.6 on Windows Server 2003 Service Pack 2:
WindowsServer2003-KB981350-x86-enu /norestart | | For VBScript 5.7 on Windows Server 2003 Service Pack 2:
WindowsServer2003-KB981349-x86-enu /norestart | | For VBScript 5.8 on Windows Server 2003 Service Pack 2:
IE8-WindowsServer2003-KB981332-x86-enu /norestart | | For VBScript 5.6 on Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981350-x64-enu /norestart | | For VBScript 5.7 on Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB981349-x64-enu /norestart | | For VBScript 5.8 on Windows Server 2003 x64 Edition Service Pack 2:
IE8-WindowsServer2003.WindowsXP-KB981332-x64-enu /norestart | | For VBScript 5.6 on Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB981350-ia64-enu /norestart | | For VBScript 5.7 on Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB981349-ia64-enu /norestart | Update log file | For VBScript 5.6: KB981350.log | | For VBScript 5.7: KB981349.log | | For VBScript 5.8: KB981332-IE8.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. | Removal Information | For VBScript 5.6, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981350$\Spuninst folder | | For VBScript 5.7, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB981349$\Spuninst folder | | For VBScript 5.8, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\IE8Updates\KB981332-IE8\Spuninst folder | File Information | For VBScript 5.6, see Microsoft Knowledge Base Article 981350 | | For VBScript 5.7, see Microsoft Knowledge Base Article 981349 | | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | For VBScript 5.6:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB981350\Filelist | | For VBScript 5.7:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB981349\Filelist | | For VBScript 5.8:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB981332-IE8\Filelist |
Installing the Update When you install this security update, 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. If 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. For more information about the 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed. | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /overwriteoem | Overwrites OEM files without prompting. | /nobackup | Does not back up files needed for uninstall. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. | /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. | /extract[:path] | Extracts files without starting the Setup program. | /ER | Enables extended error reporting. | /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note 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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /passive | Unattended 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. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed. | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Displays a dialog box prompting the local user to allow a restart. | /forceappsclose | Forces other programs to close when the computer shuts down. | /log:path | Allows the redirection of installation log files. |
Verifying that the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. | 5. | On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note 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. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files. |
| Windows Vista (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.7 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB981349-x86 /quiet | | For VBScript 5.8 on all supported 32-bit editions of Windows Vista:
IE8-Windows6.0-KB981332-x86 /quiet | | For VBScript 5.7 on all supported x64-based editions of Windows Vista:
Windows6.0-KB981349-x64 /quiet | | For VBScript 5.8 on all supported x64-based editions of Windows Vista:
IE8-Windows6.0-KB981332-x64 /quiet | Installing without restarting | For VBScript 5.7 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB981349-x86 /quiet /norestart | | For VBScript 5.8 on all supported 32-bit editions of Windows Vista:
IE8-Windows6.0-KB981332-x86 /quiet /norestart | | For VBScript 5.7 on all supported x64-based editions of Windows Vista:
Windows6.0-KB981349-x64 /quiet /norestart | | For VBScript 5.8 on all supported x64-based editions of Windows Vista:
IE8-Windows6.0-KB981332-x64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable. | Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. | File Information | For VBScript 5.7, see Microsoft Knowledge Base Article 981349 | | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
| Windows Server 2008 (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.7 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB981349-x86 /quiet | | For VBScript 5.8 on all supported 32-bit editions of Windows Server 2008:
IE8-Windows6.0-KB981332-x86 /quiet | | For VBScript 5.7 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB981349 -x64 /quiet | | For VBScript 5.8 on all supported x64-based editions of Windows Server 2008:
IE8-Windows6.0-KB981332 -x64 /quiet | | For VBScript 5.7 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB981349-ia64 /quiet | Installing without restarting | For VBScript 5.7 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB981349-x86 /quiet /norestart | | For VBScript 5.8 on all supported 32-bit editions of Windows Server 2008:
IE8-Windows6.0-KB981332-x86 /quiet /norestart | | For VBScript 5.7 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB981349 -x64 /quiet /norestart | | For VBScript 5.8 on all supported x64-based editions of Windows Server 2008:
IE8-Windows6.0-KB981332 -x64 /quiet /norestart | | For VBScript 5.7 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB981349-ia64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable. | Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. | File Information | For VBScript 5.7, see Microsoft Knowledge Base Article 981349 | | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.8 on all supported 32-bit editions of Windows 7:
Windows6.1-KB981332-x86 /quiet | | For VBScript 5.8 on all supported x64-based editions of Windows 7:
Windows6.1-KB981332-x64 /quiet | Installing without restarting | For VBScript 5.8 on all supported 32-bit editions of Windows 7:
Windows6.1-KB981332-x86 /quiet /norestart | | For VBScript 5.8 on all supported x64-based editions of Windows 7:
Windows6.1-KB981332-x64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable. | Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. | File Information | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
| Windows Server 2008 R2 (all editions) |
Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | For VBScript 5.8 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB981332-x64 /quiet | | For VBScript 5.8 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB981332-ia64 /quiet | Installing without restarting | For VBScript 5.8 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB981332-x64 /quiet /norestart | | For VBScript 5.8 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB981332-ia64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. | HotPatching | Not applicable. | Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. | File Information | For VBScript 5.8, see Microsoft Knowledge Base Article 981332 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
Microsoft Active Protections Program (MAPP)To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners. Support| • | Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support. | | • | International 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. |
DisclaimerThe information provided in the Microsoft Knowledge Base is provided "as is" 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. Revisions| • | V1.0 (April 13, 2010): Bulletin published. |
|