Microsoft Security Bulletin MS08-022 - Critical
Vulnerability in VBScript and JScript Scripting Engines Could Allow Remote Code Execution (944338)
Published: | Updated:
Version: 2.1
General Information
Executive Summary
This security update resolves a privately reported vulnerability in the VBScript and JScript scripting engines in Windows. 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.
This is a critical security update for all supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerability by modifying the way that the VBScript and JScript engines decode script in Web pages. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately
Known Issues. Microsoft Knowledge Base Article 944338 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 Software
The 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
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | VBScript 5.1 and JScript 5.1 | Remote Code Execution | Critical | MS06-023 |
| Microsoft Windows 2000 Service Pack 4 | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
| Windows XP Service Pack 2 | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems | VBScript 5.6 and JScript 5.6 | Remote Code Execution | Critical | MS06-023 |
Non-Affected Software
| Operating System |
|---|
| Windows Vista |
| Windows Vista x64 Edition |
| Windows Vista Service Pack 1 (all editions) |
| Windows Server 2008 (all editions) |
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this security bulletin revised on September 3, 2008?
Microsoft revised this security bulletin to correct the security update entries for Windows XP and Windows Server 2003 to include -v2 in the file package names. This is a correction to the package names only, customers who have successfully updated their systems do not need to reinstall this update.
Why was this security bulletin revised on August 12, 2008?
Microsoft revised this security bulletin to announce that important known issues were added to Microsoft Knowledge Base Article 944338. The known issues and their solutions are as follows:
- A setup issue was causing the update for VBScript 5.6 and JScript 5.6 to not be offered, and not installed, if Windows Internet Explorer 7 is installed on the system. The solution is a detection change to this security update. Customers who have successfully updated their systems do not need to reinstall this update.
- A library registration issue may occur when applying the update for VBScript 5.1 and JScript 5.1 on Microsoft Windows 2000 Service Pack 4. The solution is a workaround documented in Microsoft Knowledge Base Article 944338. Customers who have successfully updated their systems do not need to reinstall this update.
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 944338.
I am using JScript 5.1 and/or VBScript 5.1. Am I affected?
Yes, your software is affected. This update will apply to your software and change the version level to JScript 5.6 and/or VBScript 5.6. The file information in Microsoft Knowledge Base Article 944338 will apply to you.
I am using a release older than JScript 5.1 and VBScript 5.1 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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | VBScript/JScript Remote Code Execution Vulnerability - CVE-2008-0083 | Aggregate Severity Rating |
|---|---|---|
| VBScript 5.1 and JScript 5.1 on Microsoft Windows 2000 Service Pack 4 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Microsoft Windows 2000 Service Pack 4 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Windows XP Service Pack 2 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| VBScript 5.6 and JScript 5.6 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems | Critical Remote Code Execution | Critical |
VBScript/JScript Remote Code Execution Vulnerability - CVE-2008-0083
A remote code execution vulnerability exists in the way that the VBScript and JScript scripting engines decode script in Web pages. This vulnerability could allow remote code execution if a user opened a specially crafted file or visited a Web site that is running specially crafted script. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-0083.
Mitigating Factors for VBScript/JScript Remote Code Execution Vulnerability - CVE-2008-0083
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:
- 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 impacted than users who operate with administrative user rights.
- 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.
- In an e-mail-based attack of this exploit, customers who read e-mail in plain text are at less risk from this vulnerability.
- By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability, by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario.
- Systems with Internet Explorer 7, which is delivered with VBScript.dll version 5.7 and JScript.dll version 5.7, are not affected by this vulnerability.
- 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 have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
Workarounds for VBScript/JScript Remote Code Execution Vulnerability - CVE-2008-0083
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:
- Unregister the VBScript.Encode and JScript.Encode COM objects.
Warning Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.- Using the interactive method:
- Click Start, click Run, type regedit, and then click OK.
- Expand HKEY_CLASSES_ROOT.
- Click VBScript.Encode.
- Click File and select Export.
- In the Export Registry File dialog, type vbscript_encode_configuration_backup.reg
and click Save. - Press Delete.
- Click OK.
- Repeat steps 3 through 7 for JScript.Encode.
- Close any open instances of Internet Explorer.
- Using a managed deployment script:
- Create a backup copy of the registry keys using a managed deployment script containing the following commands:
regedit /e vbscript_encode_configuration_backup.reg
HKEY_CLASSES_ROOT\VBScript.Encode
regedit /e jscript_encode_configuration_backup.reg
HKEY_CLASSES_ROOT\JScript.Encode - Next save the following to a file with a .REG extension, for example, Disable_vbscript_and_jscript_encode.reg:
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\VBScript.Encode]
[-HKEY_CLASSES_ROOT\JScript.Encode] - Run the registry script created in step 2 on the target machine with the following command:
Regedit /s Disable_vbscript_and_jscript_encode.reg
- Create a backup copy of the registry keys using a managed deployment script containing the following commands:
Impact of workaround. Encoded scripts will not work but regular scripts will continue working.
How to undo the workaround.
- Using the interactive method:
- Using the interactive method:
- Click Start, click Run, type regedit, and then click OK.
- Click File and select Import.
- In the Import Registry File dialog, select
vbscript_encode_configuration_backup.reg
and click Open. - Click File and select Import.
- In the Import Registry File dialog, select
jscript_encode_configuration_backup.reg
and click Open.
- Using a managed deployment script:
- Restore the original state by running the following commands:
Regedit /s vbscript_encode_configuration_backup.reg
Regedit /s jscript_encode_configuration_backup.reg
- Restore the original state by running the following commands:
FAQ for VBScript/JScript Remote Code Execution Vulnerability - CVE-2008-0083
What is the scope of the vulnerability?
This is a remote code execution vulnerability. 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.
What causes the vulnerability?
The vulnerability is caused by the way that the VBScript and JScript scripting engines decode scripts in Web pages to allow the scripts to load into memory in order to run.
What is script decoding?
Web designers use scripting on Web pages and server-side active server pages (.ASP) to add features to Web pages. Web designers also encode these scripts to make it difficult for users to read the script embedded in the page, or to copy it and adapt it to their own purposes. When the script needs to run, the scripting engine decodes the script in order to load the script to memory.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability and then convince a user to visit the Web site. This could also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit these vulnerabilities. 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 in an Instant Messenger message that takes users to the attacker's Web 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.
What systems are primarily at risk from the vulnerability?
Client or workstation systems where Internet Explorer is used to browse Web pages and where VBScript.dll and JScript.dll versions below 5.6.0.8835 are used, are primarily at risk.
I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability?
Yes. 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 have not been added to Internet Explorer Trusted sites zone.
What is the Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:
- Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.
- Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
- Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
- Multimedia content is disabled. This setting prevents music, animations, and video clips from running.
For more information regarding Internet Explorer Enhanced Security Configuration, see the guide, Managing Internet Explorer Enhanced Security Configuration.
What does the update do?
This security update addresses the vulnerability by modifying the way that the VBScript and JScript engines decode script in Web pages. The VBScript scripting engine is named VBScript.dll; the JScript scripting engine is named JScript.dll.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers 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, Windows Update, and Office 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.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
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.
| Software | MBSA 2.0.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can 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 to Windows 2000 and later operating systems. 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.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | SCCM 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes 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. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 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.
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 | Microsoft Windows 2000 Service Pack 4: Windows2000-kb944338-x86-enu /quiet |
| Installing without restarting | Microsoft Windows 2000 Service Pack 4: Windows2000-kb944338-x86-enu /norestart |
| Update log file | Microsoft Windows 2000 Service Pack 4: kb944338.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update |
| HotPatching | Not applicable |
| Removal Information | Microsoft Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB944338$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 944338 |
| Registry Key Verification | Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB944338\Filelist |
Deployment Information
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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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 | Windows XP Service Pack 2: Windowsxp-kb944338-v2-x86-enu /quiet |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb944338-v2-x64-enu /quiet | |
| Installing without restarting | Windows XP Service Pack 2: Windowsxp-kb944338-v2-x86-enu /norestart |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb944338-v2-x64-enu /norestart | |
| Update log file | KB944338-v2.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB944338-v2$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 944338 |
| Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB944338-v2\Filelist |
| For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB944338-v2\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.
Deployment Information
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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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 all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb944338-v2-x86-enu /quiet |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB944338-v2-x64-enu /quiet | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB944338-v2-ia64-enu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb944338-v2-x86-enu /norestart |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB944338-v2-x64-enu /norestart | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB944338-v2-ia64-enu /norestart | |
| Update log file | KB944338-v2.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB944338-v2$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 944338 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB944338-v2\Filelist |
Deployment Information
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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /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. |
| Restart Options | |
| /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. |
| Special Options | |
| /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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Peter Ferrie of Symantec for reporting the VBScript/Jscript Remote Code Execution Vulnerability (CVE-2008-0083).
Support
- Customers 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.
- 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.
Disclaimer
The 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 8, 2008): Bulletin published.
- V1.1 (April 9, 2008): Bulletin updated. Combined JScript with VBScript in the Vulnerability Severity rating table.
- V2.0 (August 12, 2008): Added known issues link. Also added an entry to the section, Frequently Asked Questions (FAQ) Related to this Security Update, about the known issues and solutions. The solutions include a deployment change for this security update for one issue and a workaround for another. Customers who have successfully updated their systems do not need to reinstall this update.
- V2.1 (September 3, 2008): Corrected security update entries for Windows XP and Windows Server 2003 to include -v2 in the file package names. This is a correction to the package names only, customers who have successfully updated their systems do not need to reinstall this update.