• 28 minutes to read

Security Bulletin

Microsoft Security Bulletin MS08-006 - Important

Vulnerability in Internet Information Services Could Allow Remote Code Execution (942830)

Published: February 12, 2008 | Updated: February 20, 2008

Version: 1.1

General Information

Executive Summary

This important update resolves a privately reported vulnerability in Internet Information Services (IIS). A remote code execution vulnerability exists in the way that IIS handles input to ASP Web pages. An attacker who successfully exploited this vulnerability could then perform actions on the IIS server with the same rights as the Worker Process Identity (WPI). The WPI is configured with Network Service account privileges by default. IIS servers with ASP pages whose application pools are configured with a WPI that uses an account with administrative privileges could be more seriously impacted than IIS servers whose application pool is configured with the default WPI settings.

The security update is rated important for Microsoft Internet Information Services on all supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

For more information about these vulnerabilities, see the Frequently Asked Questions (FAQ) subsection under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. None

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
Windows XP Professional Service Pack 2 Microsoft Internet Information Services 5.1 Remote Code Execution Important MS06-034
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Microsoft Internet Information Services 6.0 Remote Code Execution Important MS06-034
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft Internet Information Services 6.0 Remote Code Execution Important MS06-034
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft Internet Information Services 6.0 Remote Code Execution Important MS06-034
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Microsoft Internet Information Services 6.0 Remote Code Execution Important MS06-034

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows Vista
Windows Vista x64 Edition
Windows Vista Service Pack 1 (all editions)
Windows Server 2008 (all editions)

Note Supported editions of Windows Small Business Server 2003 contain the same affected code as Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2. However, for the ASP Vulnerability (CVE-2008-0075), default configurations of Windows Small Business Server 2003 have a greater exposure to the same vulnerability and therefore merit a severity rating of Critical.

I am using an older version 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 versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions 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 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 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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software ASP Vulnerability - CVE-2008-0075 Aggregate Severity Rating
Microsoft Internet Information Services 5.1 on Windows XP Professional Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft Internet Information Services 6.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Important 
Remote Code Execution		 Important
ASP Vulnerability - CVE-2008-0075 --------------------------------- A remote code execution vulnerability exists in the way that Internet Information Services handles input to ASP Web pages. An attacker could exploit the vulnerability by passing malicious input to a Web site’s ASP page. An attacker who successfully exploited this vulnerability could then perform any actions on the IIS Server with the same rights as the Worker Process Identity (WPI), which by default is configured with Network Service account privileges. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2008-0075](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-0075). #### Mitigating Factors for ASP Vulnerability - CVE-2008-0075 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: - IIS 5.1 is not part of a default install of Windows XP Professional Service Pack 2. - On supported editions of Windows Server 2003, IIS is not installed or enabled by default. - On supported editions of Windows Server 2003, if IIS is enabled, classic ASP is not installed or enabled by default. - On supported editions of Windows Server 2003, if IIS is enabled and classic ASP is used, an attacker who successfully exploited this vulnerability could only obtain Network Service account privileges by default. By default, Network Service account privileges have the same user rights as an authenticated user. - ASP.NET is not affected by this vulnerability. Customers who have only ASP.NET installed and not ASP are not at risk from this vulnerability. #### Workarounds for ASP Vulnerability - CVE-2008-0075 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: - **On Windows Server 2003, disable classic ASP** To disable classic ASP, follow these steps: 1. Click **Start**, click **Administrative Tools**, and then click **Internet Information Services (IIS) Manager**. 2. Click the **plus sign** (+) next to the server’s name and then click the **Web Service Extensions** folder. 3. Click to highlight **Active Server Pages** in the right pane and then click **Prohibit.** **Impact of workaround.**Users will be unable to use classic ASP pages. **How to undo the workaround.**To undo the workaround, follow steps 1 through 3 above and click **Allow** when highlighting **Active Server Pages**. #### FAQ for ASP Vulnerability - CVE-2008-0075 **What is the scope of the vulnerability?** This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could then perform actions on the IIS server with the same rights as the Worker Process Identity (WPI), which by default is configured with Network Service account privileges. **What causes the vulnerability?** The vulnerability is caused by the way that Internet Information Services incorrectly processes input to ASP pages. **What might an attacker use the vulnerability to do?** An attacker who successfully exploited this vulnerability could then perform actions on the IIS Server with the same rights as the Worker Process Identity (WPI), which is configured with Network Service account privileges by default. Services configured with Network Service account privileges obtain authenticated user level access, not administrative level access. For more information see [NetworkService Account](http://msdn2.microsoft.com/en-us/library/ms684272(vs.85).aspx). IIS servers whose application pool is configured with a WPI that uses an account with administrative privileges could be more seriously impacted than IIS servers whose application pool is configured with the default WPI settings. The Network Service account uses the computer's credentials when it authenticates remotely, but has a greatly reduced privilege level on the server itself and, therefore, does not have local administrator privileges. For more information see [NetworkService Account](http://msdn2.microsoft.com/en-us/library/ms684272(vs.85).aspx), [IIS and Built-in Accounts (IIS 6.0)](http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx), [Configuring Worker Process Identities (IIS 6.0)](http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/76be66e2-1db1-432e-95be-14ff59c2ec75.mspx), and [Configuring Application Pools in IIS 6.0 (IIS 6.0)](http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/2a231dcb-d786-4b6d-b3ba-bda04061a5e7.mspx). **How could an attacker exploit the vulnerability?** An attacker could pass specially crafted input to an ASP page. The ASP page could already exist or could be uploaded by a user in a hosted environment. **What are worker processes for IIS?** Worker processes are processes that execute the server-side processing tasks for a web server**.** For information on worker processes and how they are implemented in IIS 6.0 see [Worker Processes (IIS 6.0)](http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/29f53968-0115-451f-b26d-5ad58d87b5d1.mspx). Additional information on worker processes and how they execute Web-based applications in isolation see [Worker Process Isolation Mode (IIS 6.0)](http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/333f3410-b566-49bc-8399-57bcc404db8c.mspx). **What is ASP?** Microsoft Active Server Pages (ASP) is a server-side scripting technology that can be used to create dynamic and interactive Web applications. An ASP page is an HTML page that contains server-side scripts that are processed by the Web server before being sent to the user's browser. **What systems are primarily at risk from the vulnerability?** Windows Server 2003 and Windows XP Professional Web servers are at risk if IIS and ASP are enabled. Web hosting providers that allow their customers to upload ASP pages to their hosted Web sites are at increased risk. **What does the update do?** The update removes the vulnerability by changing the way that Internet Information Services processes input to ASP pages. **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. **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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130), and [Office Update](http://go.microsoft.com/fwlink/?linkid=21135). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). 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](http://go.microsoft.com/fwlink/?linkid=96155). 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](http://go.microsoft.com/fwlink/?linkid=97900). **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](http://support.microsoft.com/kb/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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.0.1 | |-------------------------------------------------------------------------------------------------------------------|------------| | Windows XP Professional 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](http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx). **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](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 | SCCM 2007 | |-------------------------------------------------------------------------------------------------------------------|---------|----------|-----------| | Windows XP Professional Service Pack 2 | Yes | Yes | Yes | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | Yes | Yes | | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | Yes | Yes | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes | Yes | For SMS 2.0, the SMS SUS Feature Pack, 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](http://technet.microsoft.com/en-us/sms/bb676799.aspx). 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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). 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](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). 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](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723): Summary list of monthly detection and deployment guidance articles. Security Update Information --------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### 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 all supported 32-bit editions of Windows XP: Windowsxp-kb942830-x86-enu /quiet For all supported x64-based Editions of Windows XP Professional: Windowsserver2003.Windows XP-KB942830-x64-enu /quiet
Installing without restarting For all supported 32-bit editions of Windows XP: WindowsXP-KB942830-x86-enu /norestart For all supported x64-based editions of Windows XP Professional: Windowsserver2003.Windows XP-KB942830-x64-enu /norestart
Update log file KB942830.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB942830$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB942830\Filelist For all supported x64-based editions of Windows XP Professional: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB942830\Filelist

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Windows XP:

File Name Version Date Time Size Folder
asp.dll 5.1.2600.3291 10-Jan-2008 18:44 369,664 SP2GDR
asp.dll 5.1.2600.3291 10-Jan-2008 18:36 369,664 SP2QFE

For all supported x64-based editions of Windows XP Professional:

File Name Version Date Time Size CPU Folder
asp.dll 6.0.3790.3050 27-Nov-2007 16:56 610,816 X64 SP1GDR
wasp.dll 6.0.3790.3050 27-Nov-2007 16:56 378,368 X86 SP1GDR\wow
asp.dll 6.0.3790.3050 27-Nov-2007 16:56 611,840 X64 SP1QFE
wasp.dll 6.0.3790.3050 27-Nov-2007 16:56 379,904 X86 SP1QFE\wow
asp.dll 6.0.3790.4195 27-Nov-2007 17:03 621,568 X64 SP2GDR
wasp.dll 6.0.3790.4195 27-Nov-2007 17:03 388,608 X86 SP2GDR\wow
asp.dll 6.0.3790.4195 27-Nov-2007 16:55 622,080 X64 SP2QFE
wasp.dll 6.0.3790.4195 27-Nov-2007 16:55 388,608 X86 SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

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.

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. This security update supports the following setup switches.

Supported Security Update Installation 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** Display 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](http://support.microsoft.com/kb/262841). For more information about the Update.exe installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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** Display 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 versions of Microsoft Windows, the following steps may be different on your computer. 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 version of the operating system or programs installed, 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 computer 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-KB942830-x86-enu /quiet
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB942830-ia64-enu /quiet
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB942830-x64-enu /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB942830-x86-enu /norestart
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB942830-ia64-enu /norestart
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB942830-x64-enu /norestart
Update log file KB942830.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
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 SP uninstall tool at %Windir%\$NTUninstallKB942830$\Spuninst
File Information See the next subsection, File Information, for the full file manifest
Registry Key Verification For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB942830\Filelist

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Windows Server 2003:

File Name Version Date Time Size Folder
asp.dll 6.0.3790.3050 27-Nov-2007 03:01 378,368 SP1GDR
asp.dll 6.0.3790.3050 27-Nov-2007 02:37 379,904 SP1QFE
asp.dll 6.0.3790.4195 27-Nov-2007 02:43 388,608 SP2GDR
asp.dll 6.0.3790.4195 27-Nov-2007 02:57 388,608 SP2QFE

For all supported Itanium-based editions of Windows Server 2003:

File Name Version Date Time Size CPU Folder
asp.dll 6.0.3790.3050 27-Nov-2007 16:57 1,059,840 IA-64 SP1GDR
wasp.dll 6.0.3790.3050 27-Nov-2007 16:57 378,368 X86 SP1GDR\wow
asp.dll 6.0.3790.3050 27-Nov-2007 16:56 1,061,888 IA-64 SP1QFE
wasp.dll 6.0.3790.3050 27-Nov-2007 16:56 379,904 X86 SP1QFE\wow
asp.dll 6.0.3790.4195 27-Nov-2007 17:00 1,071,616 IA-64 SP2GDR
wasp.dll 6.0.3790.4195 27-Nov-2007 17:00 388,608 X86 SP2GDR\wow
asp.dll 6.0.3790.4195 27-Nov-2007 16:57 1,071,616 IA-64 SP2QFE
wasp.dll 6.0.3790.4195 27-Nov-2007 16:57 388,608 X86 SP2QFE\wow

For all supported x64-based editions of Windows Server 2003:

File Name Version Date Time Size CPU Folder
asp.dll 6.0.3790.3050 27-Nov-2007 16:56 610,816 X64 SP1GDR
wasp.dll 6.0.3790.3050 27-Nov-2007 16:56 378,368 X86 SP1GDR\wow
asp.dll 6.0.3790.3050 27-Nov-2007 16:56 611,840 X64 SP1QFE
wasp.dll 6.0.3790.3050 27-Nov-2007 16:56 379,904 X86 SP1QFE\wow
asp.dll 6.0.3790.4195 27-Nov-2007 17:03 621,568 X64 SP2GDR
wasp.dll 6.0.3790.4195 27-Nov-2007 17:03 388,608 X86 SP2GDR\wow
asp.dll 6.0.3790.4195 27-Nov-2007 16:55 622,080 X64 SP2QFE
wasp.dll 6.0.3790.4195 27-Nov-2007 16:55 388,608 X86 SP2QFE\wow

Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

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.

Supported Security Update Installation 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** Display 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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** Display 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.

    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.

Other Information

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 (February 12, 2008) Bulletin published.
  • V1.1 (February 20, 2008) Bulletin updated: update filenames changed in the file information table for all supported 32-bit editions of Windows XP.

Built at 2014-04-18T13:49:36Z-07:00