Microsoft Security Bulletin MS04-032 - Critical
Security Update for Microsoft Windows (840987)
Updated:
Version: 1.1
Issued: October 12, 2004
Version: 1.1
Summary
Who should read this document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should install the update immediately.
Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: Microsoft Knowledge Base Article 840987 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 840987.
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update
- Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 – Download the update
- Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update
- Microsoft Windows XP and Microsoft Windows XP Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Version 2003 – Download the update
- Microsoft Windows Server 2003 64-Bit Edition – Download the update
- Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems.
Non-Affected Software:
- Microsoft Windows XP Service Pack 2
The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves several newly-discovered, privately reported vulnerabilities. Each vulnerability is documented in this bulletin in its own Vulnerability Details section.
An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.
We recommend that customers apply the update immediately.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 98, 98 SE, ME | Windows NT 4.0 | Windows 2000 | Windows XP | Windows Server 2003 |
|---|---|---|---|---|---|---|
| Window Management Vulnerability - CAN-2004-0207 | Elevation of Privilege | Not Critical | Important | Important | Important | Important |
| Virtual DOS Machine Vulnerability - CAN-2004-0208 | Elevation of Privilege | None | Important | Important | Important | Important |
| Graphics Rendering Engine Vulnerability - CAN-2004-0209 | Remote Code Execution | None | None | Critical | Critical | Critical |
| Windows Kernel Vulnerability - CAN-2004-0211 | Denial of Service | None | None | None | None | Important |
| Aggregate Severity of All Vulnerabilities | Not Critical | Important | Critical | Critical | Critical |
This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.
Frequently asked questions (FAQ) related to this security update
Why was this bulletin revised on December 9, 2008?
This bulletin was revised to communicate the removal of the Windows Server 2003 package due to issues unrelated to the stability of the update or the security of the intended target systems. Customers who have already successfully applied this update need not take any action. Windows Server 2003 customers who have not applied this update and are concerned with this issue should apply the latest service pack. The applicability of this bulletin on other Windows operating systems has not changed.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.
What updates does this release replace?
This security update replaces several prior security bulletins. The security bulletin IDs and operating systems that are affected are listed in the following table.
| Bulletin ID | Windows NT 4.0 | Windows 2000 | Windows XP | Windows Server 2003 |
|---|---|---|---|---|
| MS02-071 | Replaced | Replaced | Not Replaced | Not Applicable |
| MS03-007 | Not Replaced | Replaced | Not Replaced | Not Applicable |
| MS03-013 | Replaced | Replaced | Replaced | Not Applicable |
| MS03-045 | Replaced | Replaced | Replaced | Not Replaced |
I am still using Windows XP, but extended security update support ended on September 30th, 2004. However, this bulletin has a security update for this operating system version. Why is that?
The original version of Windows XP, commonly known as Windows XP Gold or Windows XP Release to Manufacturing (RTM) version, reached the end of its extended security update support life cycle on September 30, 2004. However, the end-of-life occurred very recently. In this case, the majority of the steps that are required to address this vulnerability were completed before this date. Therefore, we have decided to release a security update for this operating system version as part of this security bulletin.
We do not anticipate doing this for future vulnerabilities that may affect this operating system version, but we reserve the right to produce updates and to make these updates available when necessary. It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Service Pack Product Life Cycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site.
For more information, see the Windows Operating System FAQ.
I am still using Microsoft Windows NT 4.0 Workstation Service Pack 6a or Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?
Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 have reached the end of their life cycles as previously documented, and Microsoft extended this support to June 30, 2004.
It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Life Cycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the following Microsoft Product Support Services Web site.
Customers who require additional support for Windows NT Workstation 4.0 SP6a must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers wihtout an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of phone numbers. When you call, ask to speak with the local Premier Support sales manager.
For more information, see the Windows Operating System FAQ.
How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?
Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.
For more information about severity ratings, visit the following Web site.
Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by any of the vulnerabilities that are addressed in this security bulletin?
No. None of these vulnerabilities are critical in severity on Windows 98, on Windows 98 Second Edition, or on Windows Millennium Edition.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
Yes. MBSA will determine if this update is required. For more information about MBSA, visit the MBSA Web site.
Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A Web site.
Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.
Vulnerability Details
Window Management Vulnerability - CAN-2004-0207:
A privilege elevation vulnerability exists in the Window Management application programming interfaces (APIs). This vulnerability could allow a logged on user to take complete control of the system.
Mitigating Factors for Window Management Vulnerability - CAN-2004-0207:
An attacker must have valid logon credentials and be able to logon locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
Workarounds for Window Management Vulnerability - CAN-2004-0207:
None.
FAQ for Window Management Vulnerability - CAN-2004-0207:
What is the scope of the vulnerability?
This is a local privilege elevation vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.
What causes the vulnerability?
Several Window Management API functions allow programs to change the properties of other programs that are running at a higher level of privilege. Programs should be limited to changing the properties of other programs that are running at the same level of privilege. The properties of the program that is running at a higher level of privilege could be changed in such a way that the change could cause an elevation of privilege for the locally logged on user.
What are the Window Management application programming interface functions?
The Windows graphical user interface (GUI) allows programs to change various properties that define that program such as the size of the window or the name of the program. The Window Management API functions are the components of the operating system that programs use to change these properties. For more information about the components that are used to build Windows programs, visit the MSDN Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
Who could exploit the vulnerability?
To exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-crafted program that could attempt to exploit the vulnerability, and thereby gain complete control over the affected system.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.
Could the vulnerability be exploited over the Internet?
No. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.
What does the update do?
The update removes the vulnerability by preventing programs from changing the properties of other programs that are running at a different level of privilege.
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 indicating 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 indicating 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
Virtual DOS Machine Vulnerability - CAN-2004-0208:
A local privilege elevation vulnerability exists in the operating system component that handles the Virtual DOS Machine (VDM) subsystem. This vulnerability could allow a logged on user to take complete control of the system.
Mitigating Factors for Virtual DOS Machine Vulnerability - CAN-2004-0208:
- An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
- Windows XP Service Pack 2 is not affected by this vulnerability.
Workarounds for Virtual DOS Machine Vulnerability - CAN-2004-0208:
None.
FAQ for Virtual DOS Machine Vulnerability - CAN-2004-0208:
What is the scope of the vulnerability?
This is a privilege elevation vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. To exploit the vulnerability, an attacker must be able to log on locally to the system and run a program.
What causes the vulnerability?
The operating system component that handles the virtual DOS machine (VDM) subsystem could be used to gain access to protected kernel memory. In certain circumstances, some privileged operating system functions might not validate system structures and could allow an attacker to execute a specially-designed program with system privileges.
What is the virtual DOS machine subsystem?
A virtual DOS machine (VDM) subsystem is an environment that emulates the MS-DOS operating system and the MS-DOS-based Windows operating system on Windows NT-based operating systems. A VDM is created whenever a user starts an MS-DOS application on a Windows NT-based operating system.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.
Who could exploit the vulnerability?
To exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.
How could an attacker exploit this vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby gain complete control over the affected system.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Could the vulnerability be exploited over the Internet?
No. An attacker must be able to log on to the specific system targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.
What does the update do?
This update modifies the way that Windows validates data when referencing memory locations that are allocated to a VDM.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information indicating 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.
How does this vulnerability relate to the virtual DOS machine vulnerability that is corrected by MS04-011?
Both vulnerabilities were in the virtual DOS machine. However, this update addresses a new vulnerability that was not addressed as part of MS04-011. MS04-011 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update does not replace MS04-011. You must install this update and the update that is provided as part of the MS04-011 security bulletin to help protect your system against both vulnerabilities.
Graphics Rendering Engine Vulnerability - CAN-2004-0209:
A remote code execution vulnerability in the rendering of Windows Metafile (WMF) and Enhanced Metafile (EMF) image formats that could allow remote code execution on an affected system. Any program that renders WMF or EMF images on the affected systems could be vulnerable to this attack. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
Mitigating Factors for Graphics Rendering Engine Vulnerability - CAN-2004-0209:
- The vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a malicious file, except potentially through previewing an email message.
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
- Windows XP Service Pack 2 is not affected by this vulnerability.
Workarounds for Graphics Rendering Engine Vulnerability - CAN-2004-0209:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
- Read e-mail messages in plain text format if you are using Outlook 2002 or later, or Outlook Express 6 SP1 or later, to help protect yourself from the HTML e-mail attack vector.
Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or later and Microsoft Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.
Digitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about enabling this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.
For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.
Impact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. In addition:
- The changes are applied to the preview pane and to open messages.
- Pictures become attachments so that they are not lost.
Note Manually viewing these pictures could allow remote code execution if you are using a vulnerable application or operating system. - Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
FAQ for Graphics Rendering Engine Vulnerability - CAN-2004-0209:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. This vulnerability could also be used to attempt to perform a local elevation of privilege or a remote denial of service.
What causes the vulnerability?
An unchecked buffer in the way that the Graphics Rendering Engine processes Windows Metafile (WMF) and Enhanced Metafile (EMF) image formats.
What are Windows Metafile (WMF) and Enhanced Metafile (EMF) image formats?
A WMF image is a 16-bit metafile format that can contain both vector information and bitmap information. It is optimized for the Windows operating system. An EMF image is a 32-bit format that can contain both vector information and bitmap information. This format is an improvement over the Windows Metafile format and contains extended features.
For more information about image types and formats, see Microsoft Knowledge Base Article 320314. Additional information about these file formats is also available at the MSDN Library Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.
How could an attacker exploit this vulnerability?
Any program that renders the affected image types could be vulnerable to this attack. Here are some examples:
- An attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.
- An attacker could create an HTML e-mail message that has a specially crafted image attached. The specially crafted image could be designed to exploit this vulnerability through Microsoft Outlook or through Outlook Express 6. An attacker could persuade the user to view the HTML e-mail message.
- An attacker could embed a specially crafted image in an Office document and then persuade the user to view the document.
- An attacker could add a specially crafted image to the local file system or onto a network share and then persuade the user to preview the folder.
- An attacker could locally log on to the system. An attacker could then run a specially-designed program that could exploit the vulnerability, and thereby gain complete control over the affected system.
An attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component (locally or remotely). To locally exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby gain complete control over the affected system.
What systems are primarily at risk from the vulnerability?
The vulnerability could be exploited on the affected systems by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an email message.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to exploit this vulnerability over the Internet.
What does the update do?
The update removes the vulnerability by modifying the way that the Graphics Rendering Engine processes Windows Metafile (WMF) and Enhanced Metafile (EMF) image formats.
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 indicating 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 indicating 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.
How does this vulnerability relate to the metafile vulnerability that is addressed by MS04-011?
Both vulnerabilities are related to the processing of WMF and EMF image formats. However, this update addresses a new vulnerability that was not addressed as part of MS04-011. MS04-011 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update does not replace MS04-011. You must install this update and the update provided as part of the MS04-011 security bulletin to help protect your system against both vulnerabilities.
How does this vulnerability relate to the JPEG processing (GDI+) vulnerability that is addressed by MS04-028?
The affected component of this vulnerability is a native operating system component and is not redistributed. The affected component in the MS04-028 JPEG processing (GDI+) vulnerability was able to be redistributed by other applications and third-party programs. Installing this operating system update helps protect against this vulnerability for all applications that could be possible attack vectors that may attempt to exploit this vulnerability. MS04-028 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update does not replace MS04-028. You must install this update and the update that is provided as part of the MS04-028 security bulletin to help protect your system against both vulnerabilities.
Windows Kernel Vulnerability - CAN-2004-0211:
A local denial of service vulnerability exists in the Windows kernel. An attacker could locally run a program that could cause the affected system to stop responding.
Mitigating Factors for Windows Kernel Vulnerability - CAN-2004-0211
- The vulnerability would not enable an attacker to gain any privileges on an affected system. This issue is strictly a denial of service vulnerability.
- Windows NT 4.0, Windows 2000, and Windows XP are not affected by this vulnerability.
Workarounds for Windows Kernel Vulnerability - CAN-2004-0211:
None.
FAQ for Windows Kernel Vulnerability - CAN-2004-0211:
What is the scope of the vulnerability?
This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. During that time, the server cannot respond to requests.
Note The denial of service vulnerability would not allow attackers to execute code or elevate their privileges, but it could cause the affected system to stop accepting requests.
What causes the vulnerability?
The Windows kernel does not properly reset some values within some CPU data structures.
What is the Windows kernel?
The Windows kernel is the core of the operating system. It provides system level services such as device management and memory management, it allocates processor time to processes, and it manages error handling. For more information about the kernel and about other operating system structures, visit the following Web site.
What might an attacker use the vulnerability to do?
An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. During that time, the server cannot respond to requests.
Who could exploit the vulnerability?
To exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed program that could exploit the vulnerability. This could cause the system to stop responding and therefore cause a denial of service condition.
What systems are primarily at risk from the vulnerability?
Terminal servers are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Could the vulnerability be exploited over the Internet?
No. An attacker must be able to log on to the specific system targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that the Windows kernel resets some values in some CPU data structures.
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 indicating 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 indicating 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.
Security Update Information
Installation Platforms and Prerequisites:
For information about the specific security update for your platform, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires a released version of Windows Server 2003.
Inclusion in Future Service Packs:
The update for this issue will be included in Windows Server 2003 Service Pack 1.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb840987-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb840987-x86-enu /norestart
For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB840987$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Windows Server 2003 Enterprise Edition, Windows Server 2003 Standard Edition, Windows Server 2003 Web Edition, and Windows Server 2003 Datacenter Edition:
Date Time Version Size File name Folder
-------------------------------------------------------------------------
27-May-2004 00:33 5.2.3790.175 2,405,888 Ntkrnlmp.exe RTMGDR
26-May-2004 23:51 5.2.3790.175 2,063,360 Ntkrnlpa.exe RTMGDR
26-May-2004 23:51 5.2.3790.175 2,105,856 Ntkrpamp.exe RTMGDR
27-May-2004 00:35 5.2.3790.175 2,206,208 Ntoskrnl.exe RTMGDR
09-Aug-2004 22:48 5.2.3790.198 1,812,992 Win32k.sys RTMGDR
01-Jun-2004 18:06 5.2.3790.177 2,407,424 Ntkrnlmp.exe RTMQFE
01-Jun-2004 17:37 5.2.3790.177 2,064,384 Ntkrnlpa.exe RTMQFE
01-Jun-2004 17:37 5.2.3790.177 2,108,928 Ntkrpamp.exe RTMQFE
01-Jun-2004 18:13 5.2.3790.177 2,207,232 Ntoskrnl.exe RTMQFE
19-Aug-2004 21:53 5.2.3790.202 1,814,528 Win32k.sys RTMQFE
Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:
Date Time Version Size Filename Platform Folder
-------------------------------------------------------------------------
10-Aug-2004 02:10 5.2.3790.198 4,952,576 Win32k.sys IA-64 RTMGDR
19-Aug-2004 21:44 5.2.3790.202 4,956,672 Win32k.sys IA-64 RTMQFE
Note When you install this security update on Windows Server 2003 or on Windows XP 64-Bit Edition Version 2003, the installer checks to see if any 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 files to your system. Otherwise, the installer copies the RTMGDR files to your system. For more information, see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note 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.
- 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 version of the operating system or programs installed, 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 following registry keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB840987\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 840987 security update into the Windows installation source files.
Windows XP (all versions)
Note For Windows XP 64-Bit Edition Version 2003, this security update is the same as the Windows Server 2003 64-Bit Edition security update.
Prerequisites
This security update requires the release version of Windows XP or Windows XP Service Pack 1 (SP1). For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue is included in Windows XP Service Pack 2.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows XP:
Windowsxp-kb840987-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
Windowsxp-kb840987-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe is located in the %Windir%\$NTUninstallKB840987$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Windows XP Home Edition, Windows XP Professional, Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, and Windows XP Media Center Edition:
Date Time Version Size File name Folder
-------------------------------------------------------------------
17-Jun-2004 17:55 5.1.2600.159 48,128 Basesrv.dll RTMQFE
17-Jun-2004 17:55 5.1.2600.151 241,664 Gdi32.dll RTMQFE
17-Jun-2004 17:55 5.1.2600.153 898,048 Kernel32.dll RTMQFE
30-Mar-2004 01:25 5.1.2600.132 36,864 Mf3216.dll RTMQFE
17-Jun-2004 17:00 5.1.2600.160 1,849,856 Ntkrnlmp.exe RTMQFE
17-Jun-2004 17:00 5.1.2600.160 1,903,872 Ntkrnlpa.exe RTMQFE
17-Jun-2004 17:00 5.1.2600.160 1,877,504 Ntkrpamp.exe RTMQFE
17-Jun-2004 17:00 5.1.2600.160 1,881,856 Ntoskrnl.exe RTMQFE
14-Jun-2004 18:27 5.1.2600.157 395,264 Ntvdm.exe RTMQFE
17-Jun-2004 17:55 5.1.2600.153 13,312 Ntvdmd.dll RTMQFE
17-Jun-2004 17:55 1,055,610 Sysmain.sdb RTMQFE
17-Jun-2004 17:55 5.1.2600.152 528,896 User32.dll RTMQFE
17-Jun-2004 17:55 5.1.2600.153 23,040 Vdmdbg.dll RTMQFE
04-Aug-2004 00:54 5.1.2600.166 1,648,384 Win32k.sys RTMQFE
17-Jun-2004 17:55 5.1.2600.153 272,896 Winsrv.dll RTMQFE
05-Jun-2004 02:21 5.1.2600.156 245,760 Wow32.dll RTMQFE
17-Jun-2004 17:58 5.1.2600.1566 47,616 Basesrv.dll SP1QFE
17-Jun-2004 17:58 5.1.2600.1561 257,536 Gdi32.dll SP1QFE
17-Jun-2004 17:58 5.1.2600.1560 930,816 Kernel32.dll SP1QFE
17-May-2004 22:48 3.10.0.103 92,224 Krnl386.exe SP1QFE
30-Mar-2004 01:48 5.1.2600.1331 36,864 Mf3216.dll SP1QFE
17-May-2004 22:43 33,840 Ntio.sys SP1QFE
17-May-2004 22:43 34,560 Ntio404.sys SP1QFE
17-May-2004 22:43 35,648 Ntio411.sys SP1QFE
17-May-2004 22:43 35,424 Ntio412.sys SP1QFE
17-May-2004 22:43 34,560 Ntio804.sys SP1QFE
17-Jun-2004 08:02 5.1.2600.1568 1,899,008 Ntkrnlmp.exe SP1QFE
17-Jun-2004 08:03 5.1.2600.1568 1,954,688 Ntkrnlpa.exe SP1QFE
17-Jun-2004 08:03 5.1.2600.1568 1,926,656 Ntkrpamp.exe SP1QFE
17-Jun-2004 17:22 5.1.2600.1568 2,051,584 Ntoskrnl.exe SP1QFE
12-Jun-2004 01:14 5.1.2600.1564 396,288 Ntvdm.exe SP1QFE
17-Jun-2004 17:58 5.1.2600.1560 13,312 Ntvdmd.dll SP1QFE
17-Jun-2004 17:58 5.1.2600.1561 560,128 User32.dll SP1QFE
17-Jun-2004 17:58 5.1.2600.1560 23,040 Vdmdbg.dll SP1QFE
05-Aug-2004 18:15 5.1.2600.1581 1,845,888 Win32k.sys SP1QFE
27-May-2004 01:38 5.1.2600.1557 483,328 Winlogon.exe SP1QFE
17-Jun-2004 17:58 5.1.2600.1561 276,992 Winsrv.dll SP1QFE
04-Jun-2004 00:43 5.1.2600.1562 245,760 Wow32.dll SP1QFE
Windows XP 64-Bit Edition Service Pack 1:
Date Time Version Size File name Platform Folder
--------------------------------------------------------------------------------
17-Jun-2004 18:05 5.1.2600.1556 885,248 Gdi32.dll IA-64 SP1QFE
30-Mar-2004 01:45 5.1.2600.1331 128,512 Mf3216.dll IA-64 SP1QFE
17-Jun-2004 18:05 5.1.2600.1557 1,483,264 User32.dll IA-64 SP1QFE
17-Jun-2004 00:45 5.1.2600.1567 5,627,520 Win32k.sys IA-64 SP1QFE
05-Aug-2004 17:27 5.1.2600.1581 5,629,952 Win32k.sys IA-64 SP1QFE
17-Jun-2004 17:58 5.1.2600.1561 237,568 Wgdi32.dll x86 SP1QFE\WOW
30-Mar-2004 01:48 5.1.2600.1331 36,864 Wmf3216.dll x86 SP1QFE\WOW
17-Jun-2004 17:58 5.1.2600.1561 556,544 Wuser32.dll x86 SP1QFE\WOW
Windows XP 64-Bit Edition Version 2003:
Date Time Version Size Filename Platform Folder
-------------------------------------------------------------------------
10-Aug-2004 02:10 5.2.3790.198 4,952,576 Win32k.sys IA-64 RTMGDR
19-Aug-2004 21:44 5.2.3790.202 4,956,672 Win32k.sys IA-64 RTMQFE
Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 versions of this security update are packaged as dual-mode packages, which contain files for both the original version of Windows XP and Windows XP Service Pack 1 (SP1). For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.
When you install the Windows XP 64-Bit Edition Version 2003 security update, the installer checks to see if any 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 files to your system. Otherwise, the installer copies the RTMGDR files to your system. For more information, see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note 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.
- 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 version of the operating system or programs installed, 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 following registry keys.
For Windows XP Home Edition, Windows XP Professional, Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP 64-Bit Edition Service Pack 1, Windows XP Tablet PC Edition, and Windows XP Media Center Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB840987\Filelist
For Windows XP 64-Bit Edition Version 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB840987\Filelist
Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 840987 security update into the Windows installation source files.
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4).
The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the Microsoft Support Lifecycle Web site.
For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
Inclusion in Future Service Packs:
The update for this issue will be included in Windows 2000 Service Pack 5.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Windows2000-kb840987-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Windows2000-kb840987-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB840987$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details on verifying an installation.
Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Date Time Version Size File name Folder
---------------------------------------------------------------------
17-Jun-2004 23:05 5.0.2195.6951 46,352 Basesrv.dll
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
17-Jun-2004 23:05 5.0.2195.6945 231,184 Gdi32.dll
17-Jun-2004 23:05 5.0.2195.6946 712,464 Kernel32.dll
19-Jun-2003 20:05 3.10.0.103 92,032 Krnl386.exe
17-Jun-2004 23:05 5.0.2195.6898 37,136 Mf3216.dll
10-Feb-2004 19:47 5.0.2195.6897 30,160 Mountmgr.sys
17-Jun-2004 23:05 5.0.2195.6824 54,544 Mpr.dll
17-Jun-2004 23:05 5.0.2195.6928 335,120 Msgina.dll
19-Jun-2003 20:05 33,824 Ntio.sys
19-Jun-2003 20:05 34,544 Ntio404.sys
19-Jun-2003 20:05 35,648 Ntio411.sys
19-Jun-2003 20:05 35,408 Ntio412.sys
19-Jun-2003 20:05 34,544 Ntio804.sys
17-Jun-2004 17:15 5.0.2195.6952 1,704,128 Ntkrnlmp.exe
17-Jun-2004 17:15 5.0.2195.6952 1,703,744 Ntkrnlpa.exe
17-Jun-2004 17:15 5.0.2195.6952 1,725,440 Ntkrpamp.exe
17-Jun-2004 17:14 5.0.2195.6952 1,680,960 Ntoskrnl.exe
27-May-2004 00:54 5.0.2195.6946 398,096 Ntvdm.exe
17-Jun-2004 23:05 5.0.2195.6946 14,096 Ntvdmd.dll
24-Mar-2004 02:17 5.0.2195.6892 90,264 Rdpwd.sys
16-May-2004 19:43 5.0.2195.6928 5,873,664 Sp3res.dll
24-Mar-2004 02:17 5.0.2195.6897 403,216 User32.dll
05-Aug-2003 22:14 5.0.2195.6794 385,808 Userenv.dll
17-Jun-2004 23:05 5.0.2195.6946 29,456 Vdmdbg.dll
10-Aug-2004 03:51 5.0.2195.6966 1,632,624 Win32k.sys
24-Aug-2004 22:59 5.0.2195.6970 182,544 Winlogon.exe
17-Jun-2004 23:05 5.0.2195.6946 244,496 Winsrv.dll
17-Jun-2004 23:05 5.0.2195.6946 239,888 Wow32.dll
17-Jun-2004 23:05 5.0.2195.6946 712,464 Kernel32.dll Uniproc
10-Aug-2004 03:51 5.0.2195.6966 1,632,624 Win32k.sys Uniproc
17-Jun-2004 23:05 5.0.2195.6946 244,496 Winsrv.dll Uniproc
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note 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.
- 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 version of the operating system or programs installed, 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB840987\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 840987 security update into the Windows installation source files.
Windows NT 4.0 (all versions)
Prerequisites
This security update requires Windows NT Server 4.0 Service Pack 6a (SP6a) or Windows NT Server 4.0 Terminal Server Edition Service Pack 6 (SP6).
Note: Microsoft Knowledge Base Article 840987 documents the currently known issues that customers may experience when they install this security update on Windows NT 4.0 Server and Windows NT 4.0 Terminal Server Edition systems. If you install software updates to a Windows NT 4.0-based computer that has a system partition that is larger than 7.8 GB, your computer may not restart correctly. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 840987.
The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
For more information about obtaining the latest service pack, see Microsoft Knowledge Base Article 152734.
Installation Information
This security update supports the following setup switches:
/y: Perform removal (only with /m or /q )
/f: Force programs to quit during the shutdown process
/n: Do not create an Uninstall folder
/z: Do not restart when the update completes
/q: Use Quiet or Unattended mode with no user interface (this switch is a superset of /m )
/m: Use Unattended mode with a user interface
/l: List the installed hotfixes
/x: Extract the files without running Setup
Note You can combine these switches into one command. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows NT Server 4.0:
Windowsnt4server-kb840987-x86-enu /q
For Windows NT Server 4.0 Terminal Server Edition:
Windowsnt4terminalserver-kb840987-x86-enu /q
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows NT Server 4.0:
Windowsnt4server-kb840987-x86-enu /z
For Windows NT Server 4.0 Terminal Server Edition:
Windowsnt4terminalserver-kb840987-x86-enu /z
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add/Remove Programs tool in Control Panel.
System administrators can also use the Hotfix.exe utility to remove this security update. The Hotfix.exe utility is located in the %Windir%\$NTUninstallKB840987$ folder. The Hotfix.exe utility supports the following setup switches:
/y: Perform removal (only with the /m or /q switch)
/f: Force programs to quit during the shutdown process
/n: Do not create an Uninstall folder
/z: Do not restart when the installation is complete
/q: Use Quiet or Unattended mode with no user interface (this switch is a superset of the /m switch)
/m: Use Unattended mode with a user interface
/l: List the installed hotfixes
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details on verifying an installation.
Windows NT Server 4.0:
Date Time Version Size File name
----------------------------------------------------------
08-Jun-2004 14:19 4.0.1381.7270 206,096 Gdi32.dll
23-Feb-2004 15:13 4.0.1381.7263 40,720 Mf3216.dll
22-Apr-2004 17:26 4.0.1381.7267 958,464 Ntkrnlmp.exe
22-Apr-2004 17:26 4.0.1381.7267 938,048 Ntoskrnl.exe
08-Jun-2004 14:19 4.0.1381.7273 326,928 User32.dll
03-Aug-2004 12:31 4.0.1381.7292 1,255,472 Win32k.sys
08-Jun-2004 14:19 4.0.1381.7260 174,864 Winsrv.dll
Windows NT Server 4.0 Terminal Server Edition:
Date Time Version Size File name
-------------------------------------------------------
20-May-2004 18:23 4.0.1381.33566 206,096 Gdi32.dll
24-Feb-2004 18:25 4.0.1381.33562 40,208 Mf3216.dll
21-May-2004 16:41 4.0.1381.33568 1,004,160 Ntkrnlmp.exe
21-May-2004 16:41 4.0.1381.33568 983,104 Ntoskrnl.exe
20-May-2004 18:23 4.0.1381.33552 332,048 User32.dll
03-Aug-2004 12:41 4.0.1381.33580 1,280,944 Win32k.sys
20-May-2004 18:23 4.0.1381.33559 196,368 Winsrv.dll
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note 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.
- 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 version of the operating system or programs installed, 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840987\File 1
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 840987 security update into the Windows installation source files.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Brett Moore of Security-Assessment.com for reporting the Window Management Vulnerability (CAN-2004-0207).
- eEye Digital Security for reporting the Virtual DOS Machine Vulnerability (CAN-2004-0208)
- Patrick Porlan working with Mark Russinovich of Winternals Software for reporting the Graphics Rendering Engine Vulnerability (CAN-2004-0209).
- hlt for reporting the Windows Kernel Vulnerability (CAN-2004-0211).
Obtaining Other Security Updates:
Updates for other security issues are available from the following locations:
- Security updates are available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available from the Windows Update Web site.
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.
Security Resources:
- The Microsoft TechNet Security Web Site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and to perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, see the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, see the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
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 12, 2004): Bulletin published
- V1.1 (December 9, 2008): Bulletin updated to add an entry in the section, Frequently asked questions (FAQ) related to this security update, about the removal of the Windows Server 2003 package. Customers who have already successfully applied this update need not take any action.