Export (0) Print
Expand All

Microsoft Security Bulletin MS04-045 - Important

Vulnerability in WINS Could Allow Remote Code Execution (870763)

Published: December 14, 2004

Version: 1.0

Issued: December 14, 2004
Version: 1.0

Summary

Who should read this document: Customers who use Microsoft Windows Internet Naming Service (WINS)

Impact of Vulnerability:  Remote Code Execution

Maximum Severity Rating: Important

Recommendation: WINS server administrators should install the update at the earliest opportunity.

Security Update Replacement: This bulletin replaces a prior security update. 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:

Non-Affected Software:

  • Microsoft Windows 2000 Professional Service Pack 3 and Microsoft Windows 2000 Professional Service Pack 4
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP 64-Bit Edition Service Pack 1
  • Microsoft Windows XP 64-Bit Edition Version 2003
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

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 several newly-discovered, public and 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 WINS administrators install the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityWindows NT 4.0 ServerWindows 2000 ServerWindows Server 2003
Name Validation Vulnerability - CAN-2004-0567Remote Code ExecutionImportantImportantImportant
Association Context Vulnerability - CAN-2004-1080Remote Code ExecutionImportantImportantImportant
Aggregate Severity of All Vulnerabilities Important Important Important

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.

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 a prior security bulletin. The security bulletin ID and operating systems that are affected are listed in the following table.

Bulletin IDWindows NT 4.0Windows 2000Windows XPWindows Server 2003
MS04-006 ReplacedReplacedNot ApplicableReplaced

I am still using Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?

Windows 2000 Service Pack 2 reached the end of its extended support life cycle as previously documented. 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 Product Lifecycle, visit the Microsoft Support Lifecycle Web site. For more information about the extended security update support period for this operating system version, visit the Microsoft Product Support Services Web site.

For more information, see the Windows Operating System Product Support Lifecycle FAQ.

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.1 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. The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.

Name Validation Vulnerability - CAN-2004-0567:

A remote code execution vulnerability exists in WINS because of the way that it handles computer name validation. An attacker could exploit the vulnerability by constructing a malicious network packet that could potentially allow remote code execution on an affected system. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for Name Validation Vulnerability - CAN-2004-0567:

  • 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.
  • By default, WINS is not installed on Windows NT Server 4.0, on Windows NT Server 4.0 Terminal Server Edition, on Windows 2000 Server, or on Windows Server 2003. By default, WINS is installed and running on Microsoft Small Business Server 2000 and on Microsoft Windows Small Business Server 2003.

    However, by default, on all versions of Microsoft Small Business Server, the WINS component communication ports are blocked from the Internet and WINS is available only on the local network.
  • On Windows Server 2003, attempts to exploit this vulnerability would most likely result in a denial of service. The WINS service automatically restarts if it fails. After the third automatic restart, WINS requires a manual restart to restore functionality.

Workarounds for Name Validation Vulnerability - CAN-2004-0567:

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.

  • Block TCP port 42 and UDP port 42 at your firewall.

    These ports are used to initiate a connection with a remote WINS server. Blocking these ports at the firewall will help prevent systems that are behind that firewall from being attacked by attempts to exploit this vulnerability. It is possible that other ports may be found that could be used to exploit this vulnerability. The ports that are listed are the most common attack vectors. We recommend blocking all inbound unsolicited communication from the Internet.

  • Remove WINS if you do not need it.

    In many organizations, WINS only provides services for legacy systems. If WINS is no longer needed, you could remove it by following this procedure. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation.

    To configure WINS components and services:

    1. Click Start, and then click Control Panel, open Add or Remove Programs.
    2. In the default Category View, click Add or Remove Programs.
    3. Click Add/Remove Windows Components.
    4. On the Windows Components Wizard page, under Components, click Networking Services, and then click Details.
    5. Click to clear the Windows Internet Naming Service (WINS) check box to remove WINS.
    6. Complete the Windows Components Wizard by following the instructions on the screen.

    Impact of Workaround: Many organizations require WINS to perform name registration and name resolution functions on their network. Administrators should not remove WINS unless they fully understand the affect that doing this will have on their network. For more information about WINS, see the WINS product documentation. Also, if an administrator is removing the WINS functionality from a server that will continue to provide shared resources on the network, the administrator must correctly reconfigure the system to use the remaining name resolution services within the local network. For more information about WINS visit the following Microsoft Web site. For more information about how to determine if you need NETBIOS or WINS name resolution and DNS configuration, visit the following Microsoft Web site.

  • On Windows 2000 Server and Windows Server 2003, use IPSec communication to secure traffic between WINS server replication partners.

    Use Internet Protocol Security (IPSec) to help protect network communications. For detailed information about how to use IPSec to help protect WINS from this issue, see Microsoft Knowledge Base Article 890710.

    Detailed information about IPSec and how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.

    Impact of Workaround: If you set up IPSec incorrectly, you may cause serious WINS replication problems on your corporate network. For additional information about IPSec security considerations, visit the following Microsoft Web site.

FAQ for Name Validation Vulnerability - CAN-2004-0567:

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.

On Windows Server 2003, the most likely attack scenario is a denial of service. An attacker who successfully exploited this vulnerability could cause WINS to fail on Windows Server 2003. On Windows Server 2003, WINS restarts automatically when it fails. After the third automatic restart, WINS requires a manual restart to restore functionality. Restarting WINS allows the service to function correctly. However, WINS could remain vulnerable to another denial of service attack.

What causes the vulnerability?
An unchecked buffer in the method that WINS uses to validate the Name value in a specially-crafted packet.

The possibility of a denial of service on Windows Server 2003 results from the presence of a security feature that was used in the development of Windows Server 2003. This security feature detects when an attempt is made to exploit a stack-based buffer overrun and reduces the chance that it can be easily exploited. This security feature can be forced to terminate the service to prevent malicious code execution. On Windows Server 2003, when an attempt is made to exploit the buffer overrun, the security feature reacts and terminates the service. This results in a denial of service condition of WINS. Because it is possible that methods may be found in the future to bypass this security feature, which could then enable code execution, customers should apply the update. For more information about these security features, visit the following Web site.

What is the Windows Internet Naming Service?
The Windows Internet Naming Service (WINS) maps IP addresses to NetBIOS computer names and vice versa. By using WINS servers, individuals can search for resources by computer name instead of by IP address. The benefits of WINS include the following:

  • Reduces NetBIOS-based broadcast traffic on subnets by permitting clients to query WINS servers to locate remote systems.
  • Supports earlier Windows and NetBIOS-based clients on the network by permitting them to browse lists for remote Windows domains without requiring a local domain controller on each subnet.
  • Supports Domain Name System (DNS)-based clients by enabling those clients to locate NetBIOS resources when WINS lookup integration is implemented.

For more information about WINS, see the WINS product documentation.

How do I know if I use WINS on my server?

By default, WINS is not installed on Windows NT Server 4.0, on Windows NT Server 4.0 Terminal Server Edition, on Windows 2000 Server, or on Windows Server 2003. By default, WINS is installed and running on Microsoft Small Business Server 2000 and on Microsoft Windows Small Business Server 2003. You can determine if WINS is installed by following this procedure. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation.

To verify WINS components and services:

  1. Click Start, and then click Control Panel, open Add or Remove Programs.
  2. In the default Category View, click Add or Remove Programs.
  3. Click Add/Remove Windows Components.
  4. On the Windows Components Wizard page, under Components, click Networking Services, and then click Details.
  5. The Windows Internet Naming Service (WINS) check box indicates if WINS is installed.
  6. Click cancel several times to exit Add/Remove Windows Components.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. The vulnerability, if exploited, could allow an attacker to cause WINS on Windows Server 2003 to stop responding to all requests.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially-crafted message to WINS on an affected server could attempt to exploit this vulnerability. Any user who could establish a connection with an affected system by using the affected ports could attempt to exploit this vulnerability.

How could an attacker exploit this vulnerability?
An attacker could attempt to exploit this vulnerability by creating a specially-crafted network message and by sending the message to the affected system. On Windows Server 2003, receipt of such a message could cause the service to fail causing a denial of service.

What systems are primarily at risk from the vulnerability?
Only Windows systems that have been configured as WINS servers are vulnerable. Windows 2000 Professional and Windows XP cannot be configured as WINS servers. Therefore, these operating systems are not affected by this vulnerability.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to 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. IT Professionals can visit the Security Center Web site.

What does the update do?
The update eliminates the vulnerability by changing the method that WINS uses to validate the name value before it passes the value 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.

How does this vulnerability relate to the WINS Vulnerability that is corrected by MS04-006?
Both vulnerabilities were in WINS. However, this update addresses a new vulnerability that was not addressed as part of MS04-006. MS04-006 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update replaces MS04-006. You may install this update to help protect your system against both vulnerabilities.

Association Context Vulnerability - CAN-2004-1080:

A remote code execution vulnerability exists in WINS because of the way that it handles association context validation. An attacker could exploit the vulnerability by constructing a malicious network packet that could potentially allow remote code execution on an affected system. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, attempts to exploit this vulnerability would most likely result in a denial of service on Windows Server 2003. The service would have to be restarted to restore functionality.

Mitigating Factors for Association Context Vulnerability - CAN-2004-1080:

  • 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.
  • By default, WINS is not installed on Windows NT Server 4.0, on Windows NT Server 4.0 Terminal Server Edition, on Windows 2000 Server, or on Windows Server 2003. By default, WINS is installed and running on Microsoft Small Business Server 2000 and on Microsoft Windows Small Business Server 2003.

    However, by default, on all versions of Microsoft Small Business Server, the WINS component communication ports are blocked from the Internet and WINS is available only on the local network.
  • On all affected operating systems, attempts to exploit this vulnerability would most likely result in a denial of service. On Windows Server 2003, the WINS service automatically restarts if it fails. After the third automatic restart, WINS requires a manual restart to restore functionality.

Workarounds for Association Context Vulnerability - CAN-2004-1080:

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.

  • Block TCP port 42 and UDP port 42 at your firewall.

    These ports are used to initiate a connection with a remote WINS server. Blocking these ports at the firewall will help prevent systems that are behind that firewall from being attacked by attempts to exploit this vulnerability. It is possible that other ports may be found that could be used to exploit this vulnerability. The ports that are listed are the most common attack vectors. We recommend blocking all inbound unsolicited communication from the Internet.

  • Remove WINS if you do not need it.

    In many organizations, WINS only provides services for legacy systems. If WINS is no longer needed, you could remove it by following this procedure. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation.

    To configure WINS components and services:

    1. Click Start, and then click Control Panel, open Add or Remove Programs.
    2. In the default Category View, click Add or Remove Programs.
    3. Click Add/Remove Windows Components.
    4. On the Windows Components Wizard page, under Components, click Networking Services, and then click Details.
    5. Click to clear the Windows Internet Naming Service (WINS) check box to remove WINS.
    6. Complete the Windows Components Wizard by following the instructions on the screen.

    Impact of Workaround: Many organizations require WINS to perform name registration and name resolution functions on their network. Administrators should not remove WINS unless they fully understand the affect that doing this will have on their network. For more information about WINS, see the WINS product documentation. Also, if an administrator is removing the WINS functionality from a server that will continue to provide shared resources on the network, the administrator must correctly reconfigure the system to use the remaining name resolution services within the local network. For more information about WINS visit the following Microsoft Web site. For more information about how to determine if you need NETBIOS or WINS name resolution and DNS configuration, visit the following Microsoft Web site.

  • On Windows 2000 Server and Windows Server 2003, use IPSec communication to secure traffic between WINS server replication partners.

    Use Internet Protocol Security (IPSec) to help protect network communications. For detailed information about how to use IPSec to help protect WINS from this issue, see HYPERLINK "http://support.microsoft.com/kb/890710"Microsoft Knowledge Base Article 890710.

    Detailed information about IPSec and how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.

    Impact of Workaround: If you set up IPSec incorrectly, you may cause serious WINS replication problems on your corporate network. For additional information about IPSec security considerations, visit the following Microsoft Web site.

FAQ for Association Context Vulnerability - CAN-2004-1080:

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. On Windows Server 2003, the most likely attack scenario is a denial of service. On Windows Server 2003 WINS restarts automatically when it fails. After the third automatic restart, WINS requires a manual restart to restore functionality. Restarting WINS allows the service to function correctly. However, WINS would remain vulnerable to another denial of service attack.

What causes the vulnerability?
The method used by WINS to validate association context data.

What is the Windows Internet Naming Service?
The Windows Internet Naming Service (WINS) maps IP addresses to NetBIOS computer names and vice versa. By using WINS servers, individuals can search for resources by computer name instead of by IP address. The benefits of WINS include the following:

  • Reduces NetBIOS-based broadcast traffic on subnets by permitting clients to query WINS servers to locate remote systems.
  • Supports earlier Windows and NetBIOS-based clients on the network by permitting them to browse lists for remote Windows domains without requiring a local domain controller on each subnet.
  • Supports Domain Name System (DNS)-based clients by enabling those clients to locate NetBIOS resources when WINS lookup integration is implemented.

For more information about WINS, see the WINS product documentation.

How do I know if I use WINS on my server?

By default, WINS is not installed on Windows NT Server 4.0, on Windows NT Server 4.0 Terminal Server Edition, on Windows 2000 Server, or on Windows Server 2003. By default, WINS is installed and running on Microsoft Small Business Server 2000 and on Microsoft Windows Small Business Server 2003. You can determine if WINS is installed by following this procedure. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation.

To verify WINS components and services:

  1. Click Start, and then click Control Panel, open Add or Remove Programs.
  2. In the default Category View, click Add or Remove Programs.
  3. Click Add/Remove Windows Components.
  4. On the Windows Components Wizard page, under Components, click Networking Services, and then click Details.
  5. The Windows Internet Naming Service (WINS) check box indicates if WINS is installed.
  6. Click cancel several times to exit Add/Remove Windows Components.

What is the association context?
The association context is a data structure that WINS maintains to store connection information about WINS replication partners.

What is wrong with the way that WINS validates the association context?
It is possible for an attacker to send a specially-crafted packet that has invalid association context data. WINS uses this data without completely validating it. This leads to a condition that most likely results in the WINS service failing.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. However, the most likely result could allow an attacker to cause WINS to stop responding to all requests on Windows Server 2003.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially-crafted message to WINS on an affected server could attempt to exploit this vulnerability. Any user who could establish a connection with an affected system by using the affected ports could attempt to exploit this vulnerability.

How could an attacker exploit this vulnerability?
An attacker could attempt to exploit this vulnerability by creating a specially-crafted network message and by sending the message to the affected system. Receipt of such a message could cause the service, most likely, to fail causing a denial of service.

What systems are primarily at risk from the vulnerability?
Only Windows systems that have been configured as WINS servers are vulnerable. Windows 2000 Professional and Windows XP cannot be configured as WINS servers. Therefore, these operating systems are not affected by this vulnerability.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to 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. IT Professionals can visit the Security Center Web site.

What does the update do?
The update eliminates the vulnerability by changing the method that WINS uses to validate the association context before use.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2004-1080. However, Microsoft also received information about this vulnerability through responsible disclosure and that researcher has received acknowledgment in this security bulletin.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2004-1080.

How does this vulnerability relate to the WINS Vulnerability that is corrected by MS04-006?
Both vulnerabilities were in WINS. However, this update addresses a new vulnerability that was not addressed as part of MS04-006. MS04-006 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update replaces MS04-006. You may install this update to help protect your system against both vulnerabilities.

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

/integrate:path  Integrates the update into the Windows source files located at the path specified.

/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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb870763-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-kb870763-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. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are 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%\$NTUninstallKB870763$\Spuninst folder. The Spuninst.exe utility 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)

Restart Options

/norestart          Do not restart when installation is complete

/forcerestart      Restart after installation

Special Options

/f                        Force other programs to close when the computer shuts down

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:

File NameVersionDateTimeSizeFolder
Wins.exe5.2.3790.23902-Dec-200403:47144,896RTMGDR
Wins.exe5.2.3790.23902-Dec-200403:47145,408RTMQFE

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

File NameVersionDateTimeSizeCPUFolder
Wins.exe5.2.3790.23902-Dec-200403:47469,504IA-64RTMGDR
Wwins.exe5.2.3790.23902-Dec-200403:47144,896x86RTMGDR\WOW
Wins.exe5.2.3790.23902-Dec-200403:47469,504IA-64RTMQFE
Wwins.exe5.2.3790.23902-Dec-200403:47145,408x86RTMQFE\WOW

Note When you install this security update on Windows Server 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 an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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 Server 2003\SP1\KB870763\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 870763 security update into the Windows installation source files.

Windows 2000 Server (all versions)

Prerequisites
For Windows 2000 Server, 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

/integrate:path  Integrates the update into the Windows source files located at the path specified.

/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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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-kb870763-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-kb870763-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

In some cases, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are 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 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%\$NTUninstallKB870763$\Spuninst folder. The Spuninst.exe utility 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)

Restart Options

/norestart          Do not restart when installation is complete

/forcerestart      Restart after installation

Special Options

/f                        Force other programs to close when the computer shuts down

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 Server Service Pack 3 and Windows 2000 Server Service Pack 4:

File NameVersionDateTimeSize
Wins.exe5.0.2195.700502-Dec-200404:03146,192

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\KB870763\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 870763 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. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb870763-x86-enu /q

To install the security update without forcing the system to restart, manually stop WINS and then use the following command at a command prompt for Windows NT Server 4.0:

Windowsnt4server-kb870763-x86-enu /z

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb870763-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. However, this restart may be avoided if you follow the instructions provided in the Deployment Information section for 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%\$NTUninstallKB870763$ 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:

File NameVersionDateTimeSize
Wins.exe4.0.1381.73292-Dec-200405:01196,880

Windows NT Server 4.0 Terminal Server Edition:

File NameVersionDateTimeSize
Wins.exe4.0.1381.3361802-Dec-200405:09196,880

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\KB870763\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 870763 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • Kostya Kortchinsky from CERT RENATER for reporting the Name Validation Vulnerability (CAN-2004-0567) and the Association Context Vulnerability (CAN-2004-1080).

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, visit 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 (December 14, 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