Export (0) Print
Expand All

Microsoft Security Bulletin MS04-031 - Important

Vulnerability in NetDDE Could Allow Remote Code Execution (841533)

Published: October 12, 2004

Version: 1.0

Issued: October 12, 2004
Version: 1.0

Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability:  Remote Code Execution

Maximum Severity Rating: Important

Recommendation: Customers should install the update at the earliest opportunity.

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: None

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 — 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:

This update resolves a newly-discovered, privately reported vulnerability. A remote code execution vulnerability exists in the Network Dynamic Data Exchange (NetDDE) services because of an unchecked buffer. The vulnerability is documented in the Vulnerability Details section of this bulletin.

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. However, the NetDDE services are not started by default and would have to be manually started, or started by an application that requires NetDDE, for an attacker to attempt to remotely exploit this vulnerability.

We recommend that customers apply the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityWindows 98, 98 SE, MEWindows NT 4.0Windows 2000Windows XPWindows Server 2003
NetDDE Vulnerability - CAN-2004-0206Remote Code ExecutionNot Critical
ImportantImportantImportantModerate

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.

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 IDWindows NT 4.0Windows 2000Windows XPWindows Server 2003
MS02-071 Not ReplacedReplacedNot ReplacedNot Applicable
MS03-045 Not ReplacedReplacedNot ReplacedNot Replaced

Note Both MS04-032 and MS04-031 security bulletins replace MS02-071and MS03-045 on Windows 2000. However, the mssecure.xml file that is used by MBSA and SUS only allows one bulletin to directly replace these prior security bulletins. In this case MS04-032 has been chosen as the official replacement for both of these prior security bulletins. While MS04-031does replace MS02-071and MS03-045 on Windows 2000, this will not be reflected by MBSA and SUS. Additionally, MS04-032 and MS04-031are not replacements for each other. Both updates must be installed to be protected from the issues documented in each of these security bulletins. However installing either of these updates for Windows 2000 will protect you from the issues documented in MS02-071and MS03-045 for Windows 2000.

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, visit 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 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 without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, 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, visit 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 the vulnerability that is addressed in this security bulletin?
No. This vulnerability is not 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.

NetDDE Vulnerability - CAN-2004-0206:

A remote code execution vulnerability exists in the NetDDE services because of an unchecked buffer. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, the NetDDE services are not started by default and would have to be manually started for an attacker to attempt to remotely exploit this vulnerability. This vulnerability could also be used to attempt to perform a local elevation of privilege or remote denial of service.

Mitigating Factors for NetDDE Vulnerability - CAN-2004-0206:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
  • On Windows Server 2003 the NetDDE services are disabled by default. Typically only administrators can change the startup type of a service. An attacker would first have to change the startup type from Disabled, and then start the service to attempt to exploit this vulnerability.
  • Disabling the NetDDE services helps prevent the possibility of a remote attack. See the Workarounds section for instructions that describe how to disable these services. Operating systems other than Windows Server 2003 have the NetDDE services startup type set to Manual instead of Disabled by default.
  • Chapter 6 of the Microsoft Solution for Securing Windows 2000 Server,Hardening the Base Windows 2000 Server recommends disabling the NetDDE services. Environments that comply with these guidelines could be at a reduced risk from this vulnerability.

Workarounds for NetDDE Vulnerability - CAN-2004-0206:

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.

  • Disable the NetDDE services

    Disabling the NetDDE services will help protect from remote attempts to exploit this vulnerability. You can disable the NetDDE services by following these steps:

    1. Click Start, and then click Control Panel (or point to Settings, and then click Control Panel).
    2. Double-click Administrative Tools.
    3. Double-click Services.
    4. Double-click Network DDE.
    5. In the Startup type list, click Disabled.
    6. Click Stop, and then click OK.
    7. Double-click Network DDE DSDM.
    8. In the Startup type list, click Disabled.
    9. Click Stop, and then click OK.

    Impact of Workaround: If the NetDDE services are disabled, messages from NetDDE applications are not transmitted. If the NetDDE services are disabled, any services that explicitly depend on the NetDDE services will not start, and an error message is logged in the system event log.

  • Use the Group Policy settings to disable NetDDE services on all affected systems that do not require this feature.
    Because NetDDE is a possible attack vector, disable it by using the Group Policy settings. You can disable the startup of this service at either the local, site, domain or organizational unit level using Group Policy object functionality in Windows 2000 or Windows Server 2003 domain environments.

    Note You may also review the Windows 2000 Hardening Guide. This guide includes information about how to disable services.

    For more information about Group Policy, visit the following Web sites:

    Impact of Workaround: If the NetDDE services are disabled, messages from NetDDE applications are not transmitted. If the NetDDE services are disabled, any services that explicitly depend on the NetDDE services will not start, and an error message is logged in the system event log.

  • Block the following at the firewall:
    • UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and 593
    • All unsolicited inbound traffic on ports greater than 1024
    • Any other specifically configured RPC port

    These ports can be used to initiate a connection to an affected system. Blocking them at the firewall will help prevent systems that are behind that firewall from attempts to exploit this vulnerability. Also, make sure that you block any other specifically configured RPC port on the remote system. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about the ports that RPC uses, visit the following Web site.

  • Use a personal firewall such as the Internet Connection Firewall , which is included with Windows XP and Windows Server 2003.

    If you use the Internet Connection Firewall feature in Windows XP or in Windows Server 2003 to help protect your Internet connection, it blocks unsolicited inbound traffic by default. We recommend blocking all unsolicited inbound communication from the Internet.

    Note This procedure does not apply to Windows XP Service Pack 2. Windows XP Server Pack 2 is not affected by this vulnerability.

    To enable the Internet Connection Firewall feature by using the Network Setup Wizard, follow these steps:

    1. Click Start, and then click Control Panel.
    2. In the default Category View, click Network and Internet Connections, and then click Setup or change your home or small office network. The Internet Connection Firewall feature is enabled when you select a configuration in the Network Setup Wizard that indicates that your system is connected directly to the Internet.

    To configure Internet Connection Firewall manually for a connection, follow these steps:

    1. Click Start, and then click Control Panel.
    2. In the default Category View, click Networking and Internet Connections, and then click Network Connections.
    3. Right-click the connection on which you want to enable Internet Connection Firewall, and then click Properties.
    4. Click the Advanced tab.
    5. Click to select the Protect my computer or network by limiting or preventing access to this computer from the Internet check box, and then click OK.

    Note If you want to enable the use of some programs and services through the firewall, click Settings on the Advanced tab, and then select the programs, protocols, and services that are required.

  • Enable advanced TCP/IP filtering on systems that support this feature.

    You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.

  • Block the affected ports by using IPSec on the affected systems.

    Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and how to apply filters is available in Microsoft Knowledge Base Articles 313190 and 813878.

FAQ for NetDDE Vulnerability - CAN-2004-0206:

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. However, the NetDDE services are not started by default and would have to be manually started for an attacker to attempt to remotely exploit this vulnerability. This vulnerability could also be used to attempt to perform a local elevation of privilege or remote denial of service.

What causes the vulnerability?
An unchecked buffer in the NetDDE services.

What is Network Dynamic Data Exchange?
Network Dynamic Data Exchange (NetDDE) allows two applications to communicate with each other over a network. This is considered an older communication method that typically has been replaced by newer technologies such as DCOM. For more information about DCOM, visit the DCOM MSDN Web Site.

What applications or services require NetDDE?
NetDDE is a considered to be an older network communication method. Applications such as the Windows for Workgroups 3.11 version of Microsoft Hearts (MSHearts) and Microsoft Chat (MSChat) application use NetDDE services. The version of Microsoft Hearts that is provided as part of Windows XP does not use NetDDE Services. The Clipbook service that is used to share a local clipboard to other systems in a network and the DDE Share Manager (DDEShare) application both require the NetDDE services. There are cases when Microsoft Excel could also use NetDDE. Microsoft Knowledge Base Article 128941 discusses how Microsoft Excel can use NetDDE. Third-party applications may also require the NetDDE services; therefore it is important to test the suggested workarounds in your organization before you deploy this update.

How can an administrator determine if NetDDE services are running?
Administrators can determine if the NetDDE services are running by viewing, Administrative Tools, Services, and searching for the NetDDE and the NetDDE DSDM services. The status of Started indicates that the services are running. See the Workarounds section of this security bulletin for instructions that explain how you can disable these services.

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?
After the NetDDE services are started, any anonymous user who could deliver a specially crafted message to the affected system could attempt to remotely exploit this vulnerability. Operating systems other than Windows XP Service Pack2 and Windows Server 2003 have the NetDDE services set to a startup type of Manual instead of Disabled. This could allow non privileged users to start the NetDDE services or could allow them to start an application that starts the NetDDE services. After the NetDDE services are started, the affected system could be vulnerable to a remote attack. To help prevent this, see the Workaround section for instructions that explain how you can disable the NetDDE services. This vulnerability could also be used to attempt to perform a local elevation of privilege.

How could an attacker exploit the vulnerability?
After a NetDDE service is started, an attacker could exploit the vulnerability by creating a specially crafted message and sending the message to an affected system, which could then cause the affected system to remotely execute code. Receipt of such a message could also cause the vulnerable system to fail in such a way that it could cause a denial of service.

To exploit this vulnerability for a local elevation of privilege, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could attempt to 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 use another program that passes parameters to the vulnerable component (locally or remotely).

What systems are primarily at risk from the vulnerability?

Workstations and terminal servers are primarily at risk. Servers are only at risk if users are given the ability to log on and to run programs. However, best practices strongly discourage allowing this.

Windows XP Service Pack 2 is not vulnerable to this issue. Windows Server 2003 is impacted at a lower severity rating because the NetDDE services startup type is set to Disabled. An attacker would first have to change the setting from Disabled to Manual or Automatic, and then start the service to attempt to remotely exploit this vulnerability. Typically, only administrators can change the startup type of a service. Operating systems other than Windows Server 2003 have the NetDDE services set to a startup type of Manual instead of Disabled. This could allow non privileged users to start the NetDDE services or allow them to start an application that starts the NetDDE services. Once the NetDDE services are started the affected system could be vulnerable to a remote attack. To help prevent this, see the Workarounds section for instructions that explain how you can disable the NetDDE services.

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 because the NetDDE service is not started by default. For more information about severity ratings, visit the following Web site.

Could the vulnerability be exploited over the Internet?
Yes. If you have manually started the NetDDE services, or if you are using applications that may have started the NetDDE services, an attacker could attempt to remotely exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT Professionals can visit the Security Center Web site.

What does the update do?
The update removes the vulnerability by modifying the way that the NetDDE services validate the length of a message before it passes the message to the allocated buffer.

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.

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 release 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-kb841533-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-kb841533-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

In some cases, this update does not require a restart. If the required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

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%\$NTUninstallKB841533$\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
-------------------------------------------------------------------------
17-Jun-2004 00:21 5.2.3790.173 16,896 Nddenb32.dll RTMGDR
16-Jun-2004 23:31 5.2.3790.184 104,448 Netdde.exe RTMGDR
17-Jun-2004 00:29 5.2.3790.173 16,896 Nddenb32.dll RTMQFE
16-Jun-2004 23:50 5.2.3790.184 104,448 Netdde.exe RTMQFE

Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:

Date Time Version Size File name Platform Folder
--------------------------------------------------------------------------------
17-Jun-2004 00:17 5.2.3790.173 38,400 Nddenb32.dll IA-64 RTMGDR
16-Jun-2004 23:46 5.2.3790.184 280,064 Netdde.exe IA-64 RTMGDR
13-Aug-2004 18:25 5.2.3790.193 16,896 Wnddenb32.dll x86 RTMGDR\WOW
17-Jul-2004 13:43 5.2.3790.193 104,448 Wnetdde.exe x86 RTMGDR\WOW
17-Jun-2004 00:28 5.2.3790.173 38,400 Nddenb32.dll IA-64 RTMQFE
16-Jun-2004 23:50 5.2.3790.184 280,064 Netdde.exe IA-64 RTMQFE
13-Aug-2004 18:18 5.2.3790.193 16,896 Wnddenb32.dll x86 RTMQFE\WOW
19-Jul-2004 17:47 5.2.3790.193 104,448 Wnetdde.exe x86 RTMQFE\WOW

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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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\KB841533\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 841533 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-kb841533-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-kb841533-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%\$NTUninstallKB841533$\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 00:24 5.1.2600.1555 16,384 Nddenb32.dll SP1QFE
16-Jun-2004 18:32 5.1.2600.1567 107,008 Netdde.exe SP1QFE
27-May-2004 01:38 5.1.2600.1557 483,328 Winlogon.exe SP1QFE
17-Jun-2004 00:22 5.1.2600.149 16,384 Nddenb32.dll RTMQFE
16-Jun-2004 19:30 5.1.2600.158 107,008 Netdde.exe RTMQFE
12-May-2004 22:15 5.1.2600.149 430,592 Winlogon.exe RTMQFE

Windows XP 64-Bit Edition Service Pack 1:

Date Time Version Size File name Platform Folder
-------------------------------------------------------------------------------
17-Jun-2004 00:37 5.1.2600.1555 39,936 Nddenb32.dll IA-64 SP1QFE
16-Jun-2004 18:32 5.1.2600.1567 315,904 Netdde.exe IA-64 SP1QFE
26-May-2004 19:29 5.1.2600.1557 647,168 Winlogon.exe IA-64 SP1QFE
17-Jun-2004 00:24 5.1.2600.1555 16,384 Wnddenb32.dll x86 SP1QFE\WOW
16-Jun-2004 18:32 5.1.2600.1567 107,008 Wnetdde.exe x86 SP1QFE\WOW

Windows XP 64-Bit Edition Version 2003:

Date Time Version Size File name Platform Folder
--------------------------------------------------------------------------------
17-Jun-2004 00:17 5.2.3790.173 38,400 Nddenb32.dll IA-64 RTMGDR
16-Jun-2004 23:46 5.2.3790.184 280,064 Netdde.exe IA-64 RTMGDR
13-Aug-2004 18:25 5.2.3790.193 16,896 Wnddenb32.dll x86 RTMGDR\WOW
17-Jul-2004 13:43 5.2.3790.193 104,448 Wnetdde.exe x86 RTMGDR\WOW
17-Jun-2004 00:28 5.2.3790.173 38,400 Nddenb32.dll IA-64 RTMQFE
16-Jun-2004 23:50 5.2.3790.184 280,064 Netdde.exe IA-64 RTMQFE
13-Aug-2004 18:18 5.2.3790.193 16,896 Wnddenb32.dll x86 RTMQFE\WOW
19-Jul-2004 17:47 5.2.3790.193 104,448 Wnetdde.exe x86 RTMQFE\WOW

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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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\KB841533\Filelist

    For Windows XP 64-Bit Edition Version 2003:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB841533\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 841533 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-kb841533-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-kb841533-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%\$NTUninstallKB841533$\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 about how to verify an installation.

Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:

Date Time Version Size File name Folder
------------------------------------------------------------------------
22-Jun-2004 01:35 5.0.2195.6951 46,352 Basesrv.dll
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
22-Jun-2004 01:35 5.0.2195.6945 231,184 Gdi32.dll
22-Jun-2004 01:35 5.0.2195.6946 712,464 Kernel32.dll
22-Jun-2004 01:35 5.0.2195.6898 37,136 Mf3216.dll
22-Jun-2004 01:35 5.0.2195.6824 54,544 Mpr.dll
22-Jun-2004 01:35 5.0.2195.6928 335,120 Msgina.dll
22-Jun-2004 01:35 5.0.2195.6922 17,168 Nddenb32.dll
16-Jun-2004 19:06 5.0.2195.6952 110,352 Netdde.exe
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
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
22-Jun-2004 01:35 5.0.2195.6946 244,496 Winsrv.dll
22-Jun-2004 01:35 5.0.2195.6946 712,464 Kernel32.dll UniProc
10-Aug-2004 03:51 5.0.2195.6966 1,632,624 Win32k.sys UniProc
22-Jun-2004 01:35 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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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\KB841533\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 841533 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).

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-kb841533-x86-enu /q

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb841533-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-kb841533-x86-enu /z

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb841533-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

In some cases, this update does not require a restart. If the required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

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%\$NTUninstallKB841533$ 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 about how to verify an installation.

Windows NT Server 4.0:

Date Time Version Size File name
----------------------------------------------------------
08-Jun-2004 14:19 4.0.1381.7268 20,240 Nddenb32.dll
16-Jun-2004 22:17 4.0.1381.7280 112,400 Netdde.exe

Windows NT Server 4.0 Terminal Server Edition:

Date Time Version Size File name
-------------------------------------------------------
17-Jun-2004 12:47 4.0.1381.33572 97,040 Cxnetdde.exe
20-May-2004 18:23 4.0.1381.33565 20,240 Nddenb32.dll
17-Jun-2004 12:47 4.0.1381.33574 50,960 Netdde.exe

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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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\KB841533\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 841533 security update into the Windows installation source files.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

Obtaining Other Security Updates:

Updates for other security issues are available from the following locations:

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:

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, visit this 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

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft