Security Bulletin

Microsoft Security Bulletin MS06-018 - Moderate

Vulnerability in Microsoft Distributed Transaction Coordinator Could Allow Denial of Service (913580)

Published: May 09, 2006 | Updated: May 24, 2006

Version: 1.1

Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Denial of Service

Maximum Severity Rating: Moderate

Recommendation: Customers should consider applying the security update.

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 XP Professional x64 Edition
  • Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003 x64 Edition
  • Microsoft Windows Server 2003 with SP1 for Itanium-based Systems
  • 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 whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary

Executive Summary:

This update resolves several newly discovered, privately reported vulnerabilities. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section of this bulletin.

We recommend that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers Impact of Vulnerability Windows 2000 Windows XP Service Pack 1 Windows XP Service Pack 2 Windows Server 2003
MSDTC Invalid Memory Access Vulnerability - CVE-2006-0034 Denial of Service Moderate Low None Low
MSDTC Denial of Service Vulnerability - CVE-2006-1184 Denial of Service Moderate Low Low Low
Aggregate Severity of All Vulnerabilities Moderate Low Low Low

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.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.

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

Bulletin ID Windows 2000 Windows XP Windows Server 2003
MS05-051 Replaced Not Replaced Not Replaced

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. 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 Lifecycle, 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 custom support for these products 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 telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

For more information, visit the Windows Operating System FAQ.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. The SMS SUS Feature pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS for detecting security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection; therefore, SMS SUIT has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office applications. The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site. However SMS 2.0 or, SMS 2003 customers that are not using the Inventory Tool for Microsoft Updates, will need to download and deploy an updated version of the Extended Security Update Inventory Tool in order receive full detection and deployment for this update. For more information about SMS, visit the SMS Web site.

Vulnerability Details

MSDTC Invalid Memory Access Vulnerability - CVE-2006-0034:

A denial of service vulnerability exists that could allow an attacker to send a specially crafted network message to an affected system. An attacker could cause the Microsoft Distributed Transaction Coordinator (MSDTC) to stop responding. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.

Mitigating Factors for MSDTC Invalid Memory Access Vulnerability - CVE-2006-0034:

  • This is a denial of service vulnerability. This issue would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected service to stop accepting requests.
  • If the Microsoft Distributed Transaction Coordinator stops responding because of an attack, services that are not dependant on the Microsoft Distributed Transaction Coordinator would continue to function normally. The affects of an attack will not typically affect the general stability of the system.
  • For customers who require the affected component, 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.

Workarounds for MSDTC Invalid Memory Access Vulnerability - CVE-2006-0034:

  • Disable the Distributed Transaction Coordinator

    Disabling the Distributed Transaction Coordinator helps protect the affected system from attempts to exploit this vulnerability. To disable the Distributed Transaction Coordinator, follow these steps:

    1. Click Start, and then click Control Panel. Alternatively, click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools.
    3. Double-click Component Services.
    4. Click Services.
    5. Double-click Distributed Transaction Coordinator.
    6. In the Startup type list, click Disabled.
    7. Click Stop, and then click OK.

    You can also stop and disable the Distributed Transaction Coordinator by using the following command at the command prompt:

    sc stop MSDTC & sc config MSDTC start= disabled

    Impact of Workaround: If you disable the Distributed Transaction Coordinator, you cannot use any service or application that is dependant on the Distributed Transaction Coordinator. This could include other applications such as SQL Server, BizTalk Server, Exchange Server, or Message Queuing. Also, this service is required in most clustering configurations. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Use the Group Policy settings to disable the Distributed Transaction Coordinator on all affected systems that do not require this feature.
    Because the Distributed Transaction Coordinator is a possible attack vector, disable it by using the Group Policy settings. You can disable the startup of this service at the local, site, domain, or organizational unit level by using Group Policy object functionality in Windows 2000 domain environments or in Windows Server 2003 domain environments. For more information about how to disable this service through logon scripts, see Microsoft Knowledge Base Article 297789

    Note You may also review the Windows 2000 Security 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 you disable the Distributed Transaction Coordinator, you cannot use any service or application that is dependant on the Distributed Transaction Coordinator. This could include other applications such as SQL Server, BizTalk Server, Exchange Server, or Message Queuing. Also, this service is required in most clustering configurations. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Disable Network DTC Access
    If you cannot install the security update, and you cannot disable the Distributed Transaction Coordinator, you may want to disable Network DTC Access. This option is only available on Windows XP and later operating system versions. This still allows local transactions to complete, but it helps protect from network based attacks that try to exploit this issue. For information about how to configure Network DTC Access, visit the following Microsoft Web site. To disable Network DTC Access, follow these steps:

    Warning Performing this procedure causes the affected service to start if it was not started previously. Stop the MSDTC service on the MSDTC tab before you close the configuration dialog boxes.

    1. Click Start, and then click Control Panel. Alternatively, click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools.
    3. Double-Click Component Services, expand Component Services, expand Computers, right-click My Computer and then click Properties,
    4. Click the MSDTC tab, and then click Security Configuration.
    5. In the Security Configuration dialog box, click to clear the Network DTC Access check box.

      Note This sets the following DWORD registry entry to 0 on non-clustering environments. Clustering environments do not read the following registry key. For Clustering environments, follow the steps that are listed in the “Disable the Distributed Transaction Coordinator” bullet point.

      HKLM\Software\Microsoft\MSDTC\Security\NetworkDtcAccess

      Note You can also apply this setting to multiple systems by using Group Policy. For more information about Group Policy, visit the following Microsoft Web site.

    6. Click OK, close the Component Services dialog box, and then close the Administrative Tools dialog box.

    Impact of Workaround: If you disable Network DTC Access, distributed transaction could fail. This could impact other applications such as SQL Server, BizTalk Server, or Message Queuing. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Block the following at the firewall:

    • All unsolicited inbound traffic on ports greater than 1024
    • Any other specifically configured RPC port

    These ports can be used to initiate a connection with MSDTC. Blocking them at the firewall will help protect 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. While RPC can use UDP ports 135, 137, 138, 445, and TCP ports 135, 139, 445, and 593, the MSDTC service is not vulnerable over those ports.

    Note Other protocols, such as Sequenced Packet Exchange (SPX) or NetBEUI, could be used to communicate with the MSDTC service. If you are using these protocols, you should block the appropriate ports for those protocols. For more information about IPX and SPX, visit the following Microsoft Web site.

  • To help protect from network-based attempts to exploit this vulnerability, use a personal firewall, such as the Internet Connection Firewall, which is included with Windows XP and with Windows Server 2003.
    By default, the Internet Connection Firewall feature in Windows XP and in Windows Server 2003 helps protect your Internet connection by blocking unsolicited incoming traffic. We recommend that you block all unsolicited incoming communication from the Internet.

    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. (Windows Sever 2003 displays this as 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. Under Windows Firewall, click Settings.
    6. Click On, and then click OK.
    7. Click the Exceptions tab. You may need to click Settings to display the exceptions tab.
    8. Verify that MSDTC.exe is not in the list of firewall exceptions, and then click OK.

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

  • To help protect from network-based attempts to exploit this vulnerability, 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.

  • To help protect from network-based attempts to exploit this vulnerability, 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 about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878. RPC uses a broad range of ports, which may make it difficult to try to secure them all by using IPsec. Microsoft Knowledge Base Article 908472 documents how to restrict RPC communication to a set of fixed ports and how to secure those ports by using IPsec.

FAQ for MSDTC Invalid Memory Access Vulnerability - CVE-2006-0034:

What is the scope of the vulnerability?
A denial of service vulnerability exists that could allow an attacker to send a specially crafted network message to an affected system. An attacker could cause the Microsoft Distributed Transaction Coordinator (MSDTC) to stop responding. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.

What causes the vulnerability?
An unchecked buffer in the MSDTC service.

What is the Microsoft Distributed Transaction Coordinator?
The Microsoft Distributed Transaction Coordinator (MSDTC) is a distributed transaction facility for Microsoft Windows platforms. MSDTC uses proven transaction processing technology. It is robust despite system failures, process failures, and communication failures; it exploits loosely coupled systems to provide scalable performance; and it is easy to install, configure, and manage. The DTC service provides the following benefits:

  • Reduces the cost of enterprise computing. The DTC provides a sophisticated, low-cost distributed transaction facility for users of networked, commodity-priced PCs and servers.
  • Simplifies application development. DTC transactions greatly simplify the application task of preserving consistency, despite failures that can occur when updating application data.
  • Provides a consistent transaction model. The DTC supports a variety of resource managers, including relational databases, object-oriented databases, file systems, document storage systems, and message queues.
  • Enables software development using distributed software components. The DTC provides a simple, object-oriented application programming interface for initiating and controlling transactions.

For information about MSDTC, visit the following Microsoft Web site.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause the affected service to stop responding.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted network message and sending the message to an affected system. The message could then cause the affected service to stop responding.

What systems are primarily at risk from the vulnerability?
Windows 2000 based versions of the Microsoft Distributed Transaction Coordinator are primarily at risk from this vulnerability because the MSDTC service is enabled by default. Windows XP SP1 and Windows Server 2003 are also at risk if the service is enabled.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try 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. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.

What does the update do?
The update removes the vulnerability by modifying the way that MDSTC validates 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.

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

MSDTC Denial of Service Vulnerability - CVE-2006-1184:

A denial of service vulnerability exists that could allow an attacker to send a specially crafted network message to an affected system. An attacker could cause the Microsoft Distributed Transaction Coordinator (MSDTC) to stop responding. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.

Mitigating Factors for MSDTC Invalid Memory Access Vulnerability - CVE-2006-1184:

  • This is a denial of service vulnerability. This issue would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected services to stop accepting requests.
  • If the Microsoft Distributed Transaction Coordinator stops responding because of an attack, services that are not dependant on the Microsoft Distributed Transaction Coordinator would continue to function normally.
  • For customers who require the affected component, 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.

Workarounds for MSDTC Denial of Service Vulnerability - CVE-2006-1184:

  • Disable the Distributed Transaction Coordinator
    Disabling the Distributed Transaction Coordinator helps protect the affected system from attempts to exploit this vulnerability. To disable the Distributed Transaction Coordinator, follow these steps:

    1. Click Start, and then click Control Panel. Alternatively, click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools.
    3. Double-click Component Services.
    4. Click Services.
    5. Double-click Distributed Transaction Coordinator.
    6. In the Startup type list, click Disabled.
    7. Click Stop, and then click OK.

    You can also stop and disable the Distributed Transaction Coordinator by using the following command at the command prompt:

    sc stop MSDTC & sc config MSDTC start= disabled

    Impact of Workaround: If you disable the Distributed Transaction Coordinator, you cannot use any service or application that is dependant on the Distributed Transaction Coordinator. This could include other applications such as SQL Server, BizTalk Server, Exchange Server, or Message Queuing. Also, this service is required in most clustering configurations. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Use the Group Policy settings to disable the Distributed Transaction Coordinator on all affected systems that do not require this feature.
    Because the Distributed Transaction Coordinator is a possible attack vector, disable it by using the Group Policy settings. You can disable the startup of this service at the local, site, domain, or organizational unit level by using Group Policy object functionality in Windows 2000 domain environments or in Windows Server 2003 domain environments. For more information about how to disable this service through logon scripts, see Microsoft Knowledge Base Article 297789

    Note You may also review the Windows 2000 Security 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 you disable the Distributed Transaction Coordinator, you cannot use any service or application that is dependant on the Distributed Transaction Coordinator. This could include other applications such as SQL Server, BizTalk Server, Exchange Server, or Message Queuing. Also, this service is required in most clustering configurations. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Disable Network DTC Access
    If you cannot install the security update, and you cannot disable the Distributed Transaction Coordinator, you may want to disable Network DTC Access. This option is only available on Windows XP and later operating system versions. This still allows local transactions to complete, but it helps protect from network based attacks that try to exploit this issue. For information about how to configure Network DTC Access, visit the following Microsoft Web site. To disable Network DTC Access, follow these steps:

    Warning Performing this procedure causes the affected service to start if it was not started previously. Stop the MSDTC service on the MSDTC tab before you close the configuration dialog boxes.

    1. Click Start, and then click Control Panel. Alternatively, click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools.
    3. Double-Click Component Services, expand Component Services, expand Computers, right-click My Computer and then click Properties,
    4. Click the MSDTC tab, and then click Security Configuration.
    5. In the Security Configuration dialog box, click to clear the Network DTC Access check box.

      Note This sets the following DWORD registry entry to 0 on non-clustering environments. Clustering environments do not read the following registry key. For Clustering environments, follow the steps that are listed in the “Disable the Distributed Transaction Coordinator” bullet point.

      HKLM\Software\Microsoft\MSDTC\Security\NetworkDtcAccess

      Note You can also apply this setting to multiple systems by using Group Policy. For more information about Group Policy, visit the following Microsoft Web site.

    6. Click OK, close the Component Services dialog box, and then close the Administrative Tools dialog box.

    Impact of Workaround: If you disable Network DTC Access, distributed transaction could fail. This could impact other applications such as SQL Server, BizTalk Server, or Message Queuing. Therefore, we recommend this workaround only on systems that cannot install the security update.

  • Block the following at the firewall:

    • All unsolicited inbound traffic on ports greater than 1024
    • Any other specifically configured RPC port

    These ports can be used to initiate a connection with MSDTC. Blocking them at the firewall will help protect 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. While RPC can use UDP ports 135, 137, 138, 445, and TCP ports 135, 139, 445, and 593, the MSDTC service is not vulnerable over those ports.

    Note Other protocols, such as Sequenced Packet Exchange (SPX) or NetBEUI, could be used to communicate with the MSDTC service. If you are using these protocols, you should block the appropriate ports for those protocols. For more information about IPX and SPX, visit the following Microsoft Web site.

  • To help protect from network-based attempts to exploit this vulnerability, use a personal firewall, such as the Internet Connection Firewall, which is included with Windows XP and with Windows Server 2003.
    By default, the Internet Connection Firewall feature in Windows XP and in Windows Server 2003 helps protect your Internet connection by blocking unsolicited incoming traffic. We recommend that you block all unsolicited incoming communication from the Internet.

    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. (Windows Sever 2003 displays this as 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. Under Windows Firewall, click Settings.
    6. Click On, and then click OK.
    7. Click the Exceptions tab. You may need to click Settings to display the exceptions tab.
    8. Verify that MSDTC.exe is not in the list of firewall exceptions, and then click OK.

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

  • To help protect from network-based attempts to exploit this vulnerability, 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.

  • To help protect from network-based attempts to exploit this vulnerability, 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 about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878. RPC uses a broad range of ports, which may make it difficult to try to secure them all by using IPsec. Microsoft Knowledge Base Article 908472 documents how to restrict RPC communication to a set of fixed ports and how to secure those ports by using IPsec.

FAQ for MSDTC Denial of Service Vulnerability - CVE-2006-1184:

What is the scope of the vulnerability?
A denial of service vulnerability exists that could allow an attacker to send a specially crafted network message to an affected system. An attacker could cause the Distributed Transaction Coordinator to stop responding. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.

What causes the vulnerability?
An unchecked buffer in the MSDTC service.

What is the Microsoft Distributed Transaction Coordinator?
The Microsoft Distributed Transaction Coordinator (MSDTC) is a distributed transaction facility for Microsoft Windows platforms. MSDTC uses proven transaction processing technology. It is robust despite system failures, process failures, and communication failures; it exploits loosely coupled systems to provide scalable performance; and it is easy to install, configure, and manage. The DTC service provides the following benefits:

  • Reduces the cost of enterprise computing. The DTC provides a sophisticated, low-cost distributed transaction facility for users of networked, commodity-priced PCs and servers.
  • Simplifies application development. DTC transactions greatly simplify the application task of preserving consistency, despite failures that can occur when updating application data.
  • Provides a consistent transaction model. The DTC supports a variety of resource managers, including relational databases, object-oriented databases, file systems, document storage systems, and message queues.
  • Enables software development using distributed software components. The DTC provides a simple, object-oriented application programming interface for initiating and controlling transactions.

For information about MSDTC, visit the following Microsoft Web site.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause the affected service to stop responding.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted network message and sending the message to an affected system. The message could then cause the affected service to stop responding.

What systems are primarily at risk from the vulnerability?
Windows 2000 based versions of the Microsoft Distributed Transaction Coordinator are primarily at risk from this vulnerability because the MSDTC service is enabled by default. Windows XP SP1 and Windows Server 2003 are also at risk if the service is enabled.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try 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. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.

What does the update do?
The update removes the vulnerability by modifying the way that MDSTC validates 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.

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

Security Update Information

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Windows Server 2003

Prerequisites This security update requires Windows Server 2003.

Inclusion in Future Service Packs The update for this issue is included in Windows Server 2003 Service Pack 1 (SP1).

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log: path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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-kb913580-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB913580.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb913580-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB913580$\Spuninst folder.

Supported Spuninst.exe Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; and Windows Small Business Server 2003:

File Name Version Date Time Size Folder
Msdtclog.dll 2001.12.4720.480 08-Feb-2006 02:13 77,824 RTMGDR
Msdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:13 443,904 RTMGDR
Msdtctm.dll 2001.12.4720.480 08-Feb-2006 02:13 962,560 RTMGDR
Msdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:13 160,768 RTMGDR
Mtxclu.dll 2001.12.4720.480 08-Feb-2006 02:13 76,288 RTMGDR
Mtxoci.dll 2001.12.4720.480 08-Feb-2006 02:13 108,032 RTMGDR
Msdtclog.dll 2001.12.4720.480 08-Feb-2006 02:11 78,848 RTMQFE
Msdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:11 448,512 RTMQFE
Msdtctm.dll 2001.12.4720.480 08-Feb-2006 02:11 965,120 RTMQFE
Msdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:11 160,768 RTMQFE
Mtxclu.dll 2001.12.4720.480 08-Feb-2006 02:11 76,288 RTMQFE
Mtxoci.dll 2001.12.4720.480 08-Feb-2006 02:11 109,056 RTMQFE

Windows Server 2003, Enterprise Edition for Itanium-based Systems and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

File Name Version Date Time Size CPU Folder
Msdtclog.dll 2001.12.4720.480 08-Feb-2006 02:11 218,624 IA-64 RTMGDR
Msdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:11 1,302,016 IA-64 RTMGDR
Msdtctm.dll 2001.12.4720.480 08-Feb-2006 02:11 3,146,240 IA-64 RTMGDR
Msdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:11 462,848 IA-64 RTMGDR
Mtxclu.dll 2001.12.4720.480 08-Feb-2006 02:11 203,776 IA-64 RTMGDR
Mtxoci.dll 2001.12.4720.480 08-Feb-2006 02:11 315,904 IA-64 RTMGDR
Wmsdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:13 443,904 x86 RTMGDR\WOW
Wmsdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:13 160,768 x86 RTMGDR\WOW
Wmtxclu.dll 2001.12.4720.480 08-Feb-2006 02:13 76,288 x86 RTMGDR\WOW
Wmtxoci.dll 2001.12.4720.480 08-Feb-2006 02:13 108,032 x86 RTMGDR\WOW
Msdtclog.dll 2001.12.4720.480 08-Feb-2006 02:06 222,208 IA-64 RTMQFE
Msdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:06 1,316,352 IA-64 RTMQFE
Msdtctm.dll 2001.12.4720.480 08-Feb-2006 02:06 3,152,896 IA-64 RTMQFE
Msdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:06 463,360 IA-64 RTMQFE
Mtxclu.dll 2001.12.4720.480 08-Feb-2006 02:06 203,776 IA-64 RTMQFE
Mtxoci.dll 2001.12.4720.480 08-Feb-2006 02:06 320,000 IA-64 RTMQFE
Wmsdtcprx.dll 2001.12.4720.480 08-Feb-2006 02:12 448,512 x86 RTMQFE\WOW
Wmsdtcuiu.dll 2001.12.4720.480 08-Feb-2006 02:12 160,768 x86 RTMQFE\WOW
Wmtxclu.dll 2001.12.4720.480 08-Feb-2006 02:12 76,288 x86 RTMQFE\WOW
Wmtxoci.dll 2001.12.4720.480 08-Feb-2006 02:12 109,056 x86 RTMQFE\WOW

Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the 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 that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA 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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification
    You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB913580\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 913580 security update into the Windows installation source files.

Windows XP (all versions)

Prerequisites This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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 Microsoft Windows XP:

Windowsxp-kb913580-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB913580.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:

Windowsxp-kb913580-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB913580$\Spuninst folder.

Supported Spuninst.exe Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

File Name Version Date Time Size Folder
Msdtcprx.dll 2001.12.4414.65 01-Mar-2006 19:44 368,640 SP1QFE
Msdtctm.dll 2001.12.4414.65 01-Mar-2006 19:44 974,336 SP1QFE
Msdtcuiu.dll 2001.12.4414.65 01-Mar-2006 19:44 150,528 SP1QFE
Mtxclu.dll 2001.12.4414.65 01-Mar-2006 19:44 64,512 SP1QFE
Mtxoci.dll 2001.12.4414.65 01-Mar-2006 19:44 83,456 SP1QFE
Xolehlp.dll 2001.12.4414.65 01-Mar-2006 19:44 11,776 SP1QFE
Msdtcprx.dll 2001.12.4414.311 01-Mar-2006 19:42 426,496 SP2GDR
Msdtctm.dll 2001.12.4414.311 01-Mar-2006 19:42 956,416 SP2GDR
Msdtcuiu.dll 2001.12.4414.311 01-Mar-2006 19:42 161,280 SP2GDR
Mtxclu.dll 2001.12.4414.311 01-Mar-2006 19:42 66,560 SP2GDR
Mtxoci.dll 2001.12.4414.311 01-Mar-2006 19:42 91,136 SP2GDR
Xolehlp.dll 2001.12.4414.311 01-Mar-2006 19:42 11,776 SP2GDR
Msdtcprx.dll 2001.12.4414.311 01-Mar-2006 19:34 426,496 SP2QFE
Msdtctm.dll 2001.12.4414.311 01-Mar-2006 19:34 956,416 SP2QFE
Msdtcuiu.dll 2001.12.4414.311 01-Mar-2006 19:34 161,280 SP2QFE
Mtxclu.dll 2001.12.4414.311 01-Mar-2006 19:34 66,560 SP2QFE
Mtxoci.dll 2001.12.4414.311 01-Mar-2006 19:34 91,136 SP2QFE
Xolehlp.dll 2001.12.4414.311 01-Mar-2006 19:34 11,776 SP2QFE

Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the 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 that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA 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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification
    You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

    For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB913580\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 913580 security update into the Windows installation source files.

Windows 2000 (all versions)

Prerequisites For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle 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 may be included in a future Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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 4:

Windows2000-kb913580-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB913580.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:

Windows2000-kb913580-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB913580$\Spuninst folder.

Supported Spuninst.exe Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

Windows 2000 Service Pack 4 and Small Business Server 2000:

File Name Version Date Time Size
Catsrv.dll 2000.2.3529.0 05-Sep-2005 20:48 165,648
Catsrvut.dll 2000.2.3529.0 05-Sep-2005 20:48 595,728
Clbcatex.dll 2000.2.3529.0 05-Sep-2005 20:48 97,040
Clbcatq.dll 2000.2.3529.0 05-Sep-2005 20:48 551,184
Colbact.dll 2000.2.3529.0 05-Sep-2005 20:48 41,744
Comadmin.dll 2000.2.3529.0 05-Sep-2005 20:48 197,904
Comrepl.dll 2000.2.3529.0 05-Sep-2005 20:48 97,552
Comsetup.dll 2000.2.3421.3529 05-Sep-2005 20:48 342,288
Comsvcs.dll 2000.2.3529.0 05-Sep-2005 20:48 1,471,248
Comuid.dll 2000.2.3529.0 05-Sep-2005 20:48 625,936
Dtcsetup.exe 2000.2.3535.0 06-Mar-2006 05:07 1,842,672
Es.dll 2000.2.3529.0 05-Sep-2005 20:48 242,448
Msdtclog.dll 2000.2.3535.0 23-Apr-2006 08:01 96,016
Msdtcprx.dll 2000.2.3535.0 23-Apr-2006 08:01 726,800
Msdtctm.dll 2000.2.3535.0 23-Apr-2006 08:01 1,202,448
Msdtcui.dll 2000.2.3535.0 23-Apr-2006 08:01 153,872
Mtstocom.exe 2000.2.3529.0 30-Aug-2005 17:35 155,408
Mtxclu.dll 2000.2.3535.0 23-Apr-2006 08:01 52,496
Mtxdm.dll 2000.2.3529.0 05-Sep-2005 20:48 26,896
Mtxlegih.dll 2000.2.3529.0 05-Sep-2005 20:48 35,600
Mtxoci.dll 2000.2.3535.0 23-Apr-2006 08:01 123,152
Ole32.dll 5.0.2195.7059 05-Sep-2005 20:48 957,712
Olecli32.dll 5.0.2195.7009 05-Sep-2005 20:48 69,392
Olecnv32.dll 5.0.2195.7059 05-Sep-2005 20:48 36,624
Rpcrt4.dll 5.0.2195.6904 12-Mar-2004 09:59 449,808
Rpcss.dll 5.0.2195.7059 05-Sep-2005 20:48 212,240
Sp3res.dll 5.0.2195.7070 23-Sep-2005 04:10 6,386,688
Stclient.dll 2000.2.3529.0 05-Sep-2005 20:48 71,440
Txfaux.dll 2000.2.3529.0 05-Sep-2005 20:48 398,608
Xolehlp.dll 2000.2.3535.0 23-Apr-2006 08:01 19,216

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA 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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification
    You may also be able to verify the files that this security update has installed by reviewing the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB913580\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 913580 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • eEye Digital Security for reporting the MSDTC Invalid Memory Access Vulnerability (CVE-2006-0034) and the MSDTC Denial of Service Vulnerability (CVE-2006-1184).
  • Xiao Chen of McAfee for reporting the MSDTC Invalid Memory Access Vulnerability (CVE-2006-0034).
  • Kai Zhang of VenusTech for reporting the MSDTC Denial of Service Vulnerability (CVE-2006-1184).

Obtaining Other Security Updates:

Updates for other security issues are available at 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 security updates by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server 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 can 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, the Microsoft Office Detection Tool, and the Enterprise Update Scanning 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 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 (May 9, 2006): Bulletin published.
  • V1.1 (May 24, 2006): Bulletin updated to reflect correct Registry Key Verification information for Microsoft Windows XP.

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