Microsoft Security Bulletin MS08-062 - Important
Vulnerability in Windows Internet Printing Service Could Allow Remote Code Execution (953155)
Published: | Updated:
Version: 2.2
General Information
Executive Summary
This update resolves a privately reported vulnerability in the Windows Internet Printing Service that could allow remote code execution. 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.
This update is rated Important for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses this vulnerability by changing the way that memory is allocated within the Internet Printing Protocol (IPP) service. 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 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
*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this Bulletin revised on October 29, 2008?
Microsoft revised this bulletin to notify customers that the update packages for Windows Server 2008 for Itanium-based Systems and all supported editions of Windows Vista have now been made available on Windows Update, Microsoft Update, Windows Software Update Services (WSUS), Systems Management Server, and System Center Configuration Manager. When this bulletin was first released, the updates for these platforms were only available on the Microsoft Download Center.
Why was this bulletin revised on October 16, 2008?
Microsoft revised this bulletin to clarify that the Windows Internet Printing service runs in the context of the Spooler service, which runs under system privileges. An attacker who successfully exploited the vulnerability described in this security bulletin could run arbitrary code under system privileges and gain complete control over the affected system.
Why was this bulletin revised on October 15, 2008?
Microsoft revised this bulletin to remove the severity rating for Windows Server 2008 for Itanium-based Systems. Also, Microsoft updated this bulletin to clarify that the update for Windows Server 2008 for Itanium-based Systems is available through the Microsoft Download Center and will be released through the other distribution channels as soon as possible.
Why is Windows Server 2008 for Itanium-based Systems and Windows Vista listed in the Affected Software table if they have no severity rating?
Windows Server 2008 for Itanium-based Systems and all supported editions of Windows Vista contain the shared print spooler component that is updated by this security update. However, because Internet Printing is not supported on Windows Server 2008 for Itanium-based Systems or Windows Vista, the exploitable vector discussed in this security bulletin is not exposed. As a defense-in-depth measure to protect against any possible new vectors identified in the future, Windows Server 2008 for Itanium-based Systems and Windows Vista customers are encouraged to apply the security update.
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 953155.
I am running one of the platforms that are listed in the affected software table. Why am I not being offered the update?
The update will only be offered to systems on which the affected component is installed. Microsoft Windows 2000 and Windows XP systems that do not have Microsoft Internet Information Services (IIS) installed are not affected and will not receive this update. Windows Server 2003 and Windows Server 2008 systems that do not have both IIS and Internet printing installed are not affected and will not receive this update.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. 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 | Integer Overflow in IPP Service Vulnerability - CVE-2008-1446 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Important Remote Code Execution | Important |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Important Remote Code Execution | Important |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Important Remote Code Execution | Important |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Remote Code Execution | Important |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Remote Code Execution | Important |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Important Remote Code Execution | Important |
| Windows Vista and Windows Vista Service Pack 1 | None | None |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | None | None |
| Windows Server 2008 for 32-bit Systems* | Important Remote Code Execution | Important |
| Windows Server 2008 for x64-based Systems* | Important Remote Code Execution | Important |
| Windows Server 2008 for Itanium-based Systems | None | None |
*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Integer Overflow in IPP Service Vulnerability - CVE-2008-1446
A remote code execution vulnerability exists on Windows systems running Microsoft Internet Information Services (IIS) with the Windows Internet Printing service enabled. This issue could allow a remote, authenticated attacker to execute arbitrary code on an affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-1446.
Mitigating Factors for Integer Overflow in IPP Service Vulnerability - CVE-2008-1446
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:
- Internet Printing Protocol (IPP) is enabled by default on IIS for Microsoft Windows 2000 and Windows XP. However, the default file permissions across all platforms are set so that IPP can only be accessed by users in the "Authenticated" group. Because of this restriction, unauthenticated users by default will not have the necessary folder permissions to exploit this vulnerability remotely.
- Installations of IIS on Windows Server 2003 are not vulnerable in their default configuration. Only Windows Server 2003 installations that have enabled the Internet Printing Protocol ISAPI filter within IIS are vulnerable. Both the Internet Printing and Active Server Pages components are necessary to enable Web-based printer management and Internet printing. If Active Server Pages component is set to "Allowed" and Internet Printing component is set to "Prohibited," only Web-based printer management is enabled. Users cannot connect to any shared printers through Internet Printing.
- Installations of IIS on Windows Server 2008 are not vulnerable by default. A computer running Windows Server 2008 can act as a client computer that uses Internet printing. Users of the computer who make print requests must be authenticated by the print server, however, before they can use any of the printers connected to that server. To enable a computer running Windows Server 2008 to act as a server supporting Internet printing, you must install the Web Server (IIS) role, the Print Services role, and the Internet Printing role service in the Print Services role.
- Exploitation of this vulnerability requires that the IIS server communicate outbound to a malicious computer on port 445. Administrators who block outbound SMB connections from their IIS server to the Internet can prevent exploitation of this vulnerability from untrusted systems.
Workarounds for Integer Overflow in IPP Service Vulnerability - CVE-2008-1446
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:
- Disable the IPP Service
To disable IPP Service in IIS 5.0 and IIS 5.1
- Open Internet Services Manager.
- Right-click the Default Website and choose Properties.
- Go to the Home Directory tab and select Configuration.
- Scroll down to find the .printer extension and the corresponding path to msw3prt.dll.
- Click Remove.
- Click OK.
- Restart the IIS Service.
Note Internet Printing can be configured via group policy as well as via the Internet Services Manager. If there is a conflict between the group policy settings and those in the Internet Service Manager, the group policy settings take precedence. If you remove Internet Printing via the Internet Services Manager, be sure to verify that it won’t be re-enabled by either local or domain group policies. (The default group policy neither enables nor disables Internet Printing.) In the MMC Group Policy snap-in, check Computer Configuration | Administrative Templates | Printing |Web-based Printing.
To disable IPP Service in IIS 6.0
- Start IIS Manager or the IIS snap-in.
- Expand * server_name, where server_name is the name of the server.
- Click Web Service Extensions.
- On the right pane, click Internet Printing, and then click Prohibited.
- Quit IIS Manager.
To disable IPP Service in IIS 7.0 on Windows Server 2008
- If ServerManager is not running, click Start, click Administrative Tools, and then click Server Manager. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)
- Expand the Roles node, and then right-click Print Services and select Remove Role Services.
- The Remove Role Services wizard will appear. If the Internet Printing option is checked then clear the check box, click Next, and then Remove to complete the wizard.
Impact of workaround. Users will not be able to connect to any shared printers through Internet Printing.
How to undo the workaround.
To enable IPP Service in IIS 5.0 and IIS 5.1
- Open Internet Services Manager.
- Right-click the Default Website and choose Properties.
- Go to the Home Directory tab and select Configuration.
- Scroll down to find the .printer extension and the corresponding path to msw3prt.dll.
- Click Add.
- In the field marked Executable, input the following:
%systemroot%\system32\msw3prt.dll - In the field marked Extension, input the following:
.printer - In the field marked Limit to, input the following:
GET,POST - Once this is complete, restart the IIS service.
To enable IPP Service in IIS 6.0
- Start IIS Manager or the IIS snap-in.
- Expand * server_name, where server_name is the name of the server.
- Click Web Service Extensions.
- On the right pane, click Internet Printing, and then click Allow.
- Quit IIS Manager.
To enable IPP Service in IIS 7.0
- If ServerManager is not running, click Start, click Administrative Tools, and then click Server Manager. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)
- Expand the Roles node, and then right-click Print Services and select Add Role Services.
- The Add Role Services wizard will appear. Check the Internet Printing option, click Next, and then Install to complete the wizard.
- Run the IIS Lockdown Tool 2.1
On Microsoft Windows 2000 running IIS 5.0 or Windows XP running IIS 5.1, the IIS Lockdown Wizard version 2.1 can be used to disable unnecessary features, including Internet Printing. To run this wizard, complete the following actions:
- Download the IIS Lockdown Tool 2.1 from here.
- Do one of the following:
To start the installation immediately, click Open or Run this program from its current location.
To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
Impact of Workaround.
Users will not be able to connect to any shared printers through Internet Printing. Additionally, the IIS Lockdown tool Users will not be able to connect to any shared printers through Internet Printing. For a complete list of changes made by the IIS Lockdown tool, see the following MSDN article.
How to undo the workaround.
To undo the changes made by IIS Lockdown, run IISlockd.exe a second time and choose to undo the changes. The undo operation restores the system settings that were in effect immediately before you previously ran IISLockdown. These details are contained in the log file \WINNT\System32\inetsrv\0blt-log. Therefore, it is important that you test the system promptly after you run IISLockdown. If an undo is required, perform it immediately.
Note The URLScan ISAPI filter that is installed as part of IIS Lockdown is not removed as part of the undo process. You can remove URLScan manually by using the ISAPI filters tab at the server level in Internet Services Manager.
FAQ for Integer Overflow in IPP Service Vulnerability - CVE-2008-1446
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.
What causes the vulnerability?
The Internet Printing Protocol (IPP) function is implemented as an ISAPI extension for IIS. There exists a remote, authenticated vulnerability in the Microsoft implementation of IPP on Windows servers running IIS. An integer overflow exists in the IPP implementation that could allow an authenticated attacker to perform remote code execution on affected IIS servers.
What is ISAPI?
ISAPI (Internet Services Application Programming Interface) is a technology that enables web developers to extend the functionality of their web servers by writing custom code that provides new services for a web server. The custom code can either be implemented in an ISAPI filter, if the new functionality provides a low-level service, or an ISAPI extension, if the new functionality provides a high-level service. In this case, the affected code is an ISAPI extension.
What's the ISAPI extension at issue here?
The affected ISAPI extension is one that implements the Internet Printing Protocol (IPP), an industry standard defined in RFCs 2910 and 2911. IPP provides a way to request printing services and learn the status of print jobs across the Internet via HTTP. For instance, using IPP, a traveling user could send a print job across the Internet, to be printed on a printer on his corporate network. The user could also find out whether the print request had completed without error.
Microsoft Windows 2000 introduced native support for Internet Printing. The Microsoft Windows 2000 implementation enables users to print directly to an URL, and to view information about print jobs via their browsers. Support for Internet Printing is enabled by default in Microsoft Windows 2000 Server versions. It can also be installed as an optional component on Microsoft Windows 2000 Professional, Windows XP, Windows Server 2003, and Windows Server 2008.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user’s system with system privileges. 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.
How could an attacker exploit the vulnerability?
An attacker could send a specially crafted HTTP POST request to a vulnerable web server that would cause the server to connect to a machine controlled by the attacker acting as a printer using IPP. The attacker would then use specially crafted responses to perform remote code execution on the target server.
What systems are primarily at risk from the vulnerability?
Workstations and servers running IIS with the Internet Printing Protocol (IPP) service enabled are primarily at risk from this vulnerability.
What does the update do?
This security update addresses this vulnerability by validating the data received from remote machines within the Internet Printing Protocol (IPP) service.
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?
Yes, Microsoft is aware of targeted attacks attempting to exploit the vulnerability. However, Microsoft 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 systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, 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.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | 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 |
| Windows Vista and Windows Vista Service Pack 1 | Yes |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Yes |
| Windows Server 2008 for 32-bit Systems | Yes |
| Windows Server 2008 for x64-based Systems | Yes |
| Windows Server 2008 for Itanium-based Systems | Yes |
For more information about MBSA 2.1, see MBSA 2.1 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 Microsoft Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition 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 |
| Windows Vista and Windows Vista Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for 32-bit Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for x64-based Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for Itanium-based Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | 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 (Configuration Manager) 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | Microsoft Windows 2000 Service Pack 4: Windows2000-kb953155-x86-enu /quiet |
| Installing without restarting | Microsoft Windows 2000 Service Pack 4: Windows2000-kb953155-x86-enu /norestart |
| Update log file | Microsoft Windows 2000 Service Pack 4: kb953155.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%\$NTUninstallKB953155$Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 953155 |
| Registry Key Verification | Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB953155\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 and Windows XP Service Pack 3: Windowsxp-kb953155-x86-enu /quiet |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb953155-x64-enu /quiet | |
| Installing without restarting | Windows XP Service Pack 2 and Windows XP Service Pack 3: Windowsxp-kb953155-x86-enu /norestart |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb953155-x64-enu /norestart | |
| Update log file | KB953155.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%\$NTUninstallKB953155$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 953155 |
| Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB953155\Filelist |
| For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB953155\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-kb953155-x86-enu /quiet |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB953155-x64-enu /quiet | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB953155-ia64-enu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb953155-x86-enu /norestart |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB953155-x64-enu /norestart | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB953155-ia64-enu /norestart | |
| Update log file | KB953155.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. Note A system restart can be avoided for Windows Server 2003 by stopping the IIS service, installing the update, and then restarting the IIS service. If the IIS service is not stopped before installing the update, then a system restart will still be required. |
| 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%\$NTUninstallKB953155$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 953155 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB953155\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.
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of Windows Vista: Windows6.0-KB953155-x86 /quiet For all supported x64-based editions of Windows Vista: Windows6.0-KB953155-x64 /quiet |
| Installing without restarting | For all supported 32-bit editions of Windows Vista: Windows6.0-KB953155-x86 /norestart /quiet For all supported x64-based editions of Windows Vista: Windows6.0-KB953155-x64 /norestart /quiet |
| 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 | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See Microsoft Knowledge Base Article 953155 |
| Registry Key Verification | Note: A registry key does not exist to validate the presence of this 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.
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 |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows Server 2008 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB953155-x86 /quiet For all supported x64-based editions of Windows Server 2008: Windows6.0-KB953155-x64 /quiet For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB953155-ia64 /quiet |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB953155-x86 /norestart /quiet For all supported x64-based editions of Windows Server 2008: Windows6.0-KB953155?-x64 /norestart /quiet For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB953155-ia64 /norestart /quiet |
| 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 | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See Microsoft Knowledge Base Article 953155 |
| Registry Key Verification | Note: A registry key does not exist to validate the presence of this 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.
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 |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- CERT/CC for reporting the Integer Overflow in IPP Service Vulnerability - CVE-2008-1446
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 (October 14, 2008): Bulletin published.
- V2.0 (October 15, 2008): Removed the severity rating for Windows Server 2008 for Itanium-based Systems. Added entries to Frequently Asked Questions (FAQ) Related to This Security Update to explain the reason for the rating change and to clarify that the update for Windows Server 2008 for Itanium-based Systems is available through the Microsoft Download Center. Also, changed the Microsoft Baseline Security Analyzer and Systems Management Server deployment summaries to "no" for Windows Server 2008 for Itanium-based Systems in the Detection and Deployment Tools and Guidance section. There were no changes to the security update binaries.
- V2.1 (October 16, 2008): Added entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, to clarify that the Windows Internet Printing service runs in the context of the Spooler service, which runs under system privileges. Also, removed references to user rights in the Executive Summary and FAQ for Integer Overflow in IPP Service Vulnerability - CVE-2008-1446 sections.
- V2.2 (October 29, 2008): Revised entries in the section, Frequently Asked Questions (FAQ) Related to This Security Update, and in the Microsoft Baseline Security Analyzer (MBSA) and Systems Management Server (SMS) detection and deployment tables in the section, Detection and Deployment Tools and Guidance, to notify customers that the update packages for Windows Server 2008 for Itanium-based Systems and all supported editions of Windows Vista have now been made available on Windows Update, Microsoft Update, Windows Software Update Services (WSUS), Systems Management Server, and System Center Configuration Manager.