Microsoft Security Bulletin MS05-051 Vulnerabilities in MSDTC and COM+ Could Allow Remote Code Execution (902400)

2005-10-13T00:00:00
ID SECURITYVULNS:DOC:9920
Type securityvulns
Reporter Securityvulns
Modified 2005-10-13T00:00:00

Description

Microsoft Security Bulletin MS05-051 Vulnerabilities in MSDTC and COM+ Could Allow Remote Code Execution (902400) Published: October 11, 2005

Version: 1.0 Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software: •

Microsoft Windows 2000 Service Pack 4 – Download the update •

Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – Download the update •

Microsoft Windows XP Professional x64 Edition – Download the update •

Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update •

Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update •

Microsoft Windows Server 2003 x64 Edition – Download the update

Non-Affected Software: •

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. Top of sectionTop of section 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.

An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

We recommend that Windows 2000 and Windows XP Service Pack 1 customers apply the update immediately. We recommend that customers using other operating system versions apply the update at the earliest opportunity.

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 Windows Server 2003 Service Pack 1

MSDTC Vulnerability - CAN-2005-2119

Remote Code Execution and Local Elevation of Privilege

Critical

Important

None

Important

None

COM+ Vulnerability - CAN-2005-1978

Remote Code Execution and Local Elevation of Privilege

Critical

Critical

Important

Important

Important

TIP Vulnerability - CAN-2005-1979

Denial of Service

Moderate

Low

Low

Low

Low

Distributed TIP Vulnerability - CAN-2005-1980

Denial of Service

Moderate

Low

Low

Low

Low

Aggregate Severity of All Vulnerabilities

Critical

Critical

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.

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

The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. •

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

The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. •

The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. Top of sectionTop of section

Vulnerability Details

MSDTC Vulnerability - CAN-2005-2119:

A remote code execution and local elevation of privilege vulnerability exists in the Microsoft Distributed Transaction Coordinator that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.

Mitigating Factors for MSDTC Vulnerability - CAN-2005-2119: •

Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1 systems are not vulnerable to this issue. •

By default, on Windows Server 2003, the Microsoft Distributed Transaction Coordinator is started, but it is not configured to support Network DTC Access. An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. However, if an administrator has enabled support for Network DTC Access, Windows Server 2003 systems could be vulnerable to remote code execution attacks by anonymous users. For information about how to configure Network DTC Access, visit the following Microsoft Web site. •

By default, on Windows XP Service Pack 1, the Microsoft Distributed Transaction Coordinator is not started. This service must be running to enable the remote attack vector. An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. However, any local user can start this service unless the service has been disabled by an administrator. As soon as this service is started, Windows XP Service Pack 1 systems could be vulnerable to remote code execution attacks by anonymous users. This is because on Windows XP Service Pack 1 systems, the Microsoft Distributed Transaction Coordinator service is configured to allow Network DTC Access. For information about how to configure Network DTC Access, visit the following Microsoft Web site. •

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.

Top of sectionTop of section

Workarounds for MSDTC Vulnerability - CAN-2005-2119:

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 in the following section. •

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

Step-by-Step Guide to Understanding the Group Policy Feature Set •

Windows 2000 Group Policy •

Group Policy in Windows Server 2003

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. Top of sectionTop of section

FAQ for MSDTC Vulnerability - CAN-2005-2119:

What is the scope of the vulnerability? On Windows 2000 this is a remote code execution vulnerability. On Windows XP Service Pack 1 and Windows Server 2003 this is a local privilege elevation vulnerability. On Windows XP Service Pack 1, this also becomes a remote code execution vulnerability if the Microsoft Distributed Transaction Coordinator is started. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? An unchecked buffer in the Microsoft Distributed Transaction Coordinator.

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 take complete control of the affected system.

Who could exploit the vulnerability? On Windows 2000, any anonymous user who could deliver a specially crafted network message to the affected system could try to exploit this vulnerability. On Windows XP Service Pack 1 and Windows Server 2003, an attacker must be able to log on locally to a system and run a program to try to exploit the vulnerability. Windows XP Service Pack 1 and Windows Server 2003 are not vulnerable to remote anonymous attack in default scenarios. User configuration is required on these operating system versions in order to create the possibility of remote attack. If attacked locally, an attacker could then run a specially-crafted application that could exploit the vulnerability and gain complete control over the affected system.

What systems are primarily at risk from the vulnerability? Windows 2000 systems are primarily at risk from this vulnerability. On Windows XP Service Pack 1 and Windows Server 2003, an attacker must have valid logon credentials to exploit this vulnerability unless user configuration has been performed that could allow remote anonymous attacks. On Windows Server 2003, if an administrator has enabled support for Network DTC Access, Windows Server 2003 systems could be vulnerable to remote code execution attacks by anonymous users. For information about how to configure Network DTC Access, visit the following Microsoft Web site. Administrators can use the registry key that is documented at the following Microsoft Web site to verify that Network DTC Access has not been enabled.

Could the vulnerability be exploited over the Internet? On Windows 2000 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 MSDTC 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. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 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. Top of sectionTop of section Top of sectionTop of section

COM+ Vulnerability - CAN-2005-1978:

A remote code execution and local elevation of privilege vulnerability exists in COM+ that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.

Mitigating Factors for COM+ Vulnerability - CAN-2005-1978: •

On Windows XP Service Pack 2, on Windows Server 2003, and on Windows Server 2003 Service Pack 1 an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely unless the attacker already has administrative permissions. •

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. Top of sectionTop of section

Workarounds for COM+ Vulnerability - CAN-2005-1978:

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 in the following section. •

Disable COM+ Disabling COM+ helps protect the affected system from attempts to exploit this vulnerability. There are different ways to disable COM+, depending on which platform you are using.

Important This bulletin contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see Microsoft Knowledge Base Article 256986.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. •

On Windows 2000, create a file that is named ~clbcatq.dll in the %windir%\system32 folder. These steps create a similar environment as the issue that is discussed in Microsoft Knowledge Based Article 246499. To disable COM+ on Windows 2000, follow these steps:

1.

Logon as an administrator.

2.

Click Start, and then click Run and then type:

echo “Workaround for KB902400” >%windir%\system32\~clbcatq.dll

3.

Restart the system. Note To re-enable COM+, delete the ~clbcatq.dll file and restart the system. •

To disable COM+ on Windows XP and Windows Server 2003, create a registry key and restart the computer to disable COM+:

On these operating system versions you can create a registry key and restart the machine to disable COM+.

1.

Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.

2.

In Registry Editor, locate the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\COM3

3.

Double-click the COM+Enabled registry entry, and then change the value to 0.

Note Make a note of the current value so that you can reverse this procedure if required.

4.

Quit Registry Editor and restart the system. •

Alternatively, you can paste the following text into a .reg file. Then, double-click the .reg file while you are logged on locally as an administrator:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3] "Com+Enabled"=dword:00000000

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.

Impact of Workaround: If you disable COM+, you cannot use any COM+ dependant applications. Customers should evaluate whether any business-critical applications rely on COM+ services before they deploy these workarounds. We recommend these workaround only on systems that cannot install the security update. For information about COM+, visit the following Microsoft Web site. •

Block the following at the firewall: •

UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and 593 •

If installed, COM Internet Services (CIS) or RPC over HTTP, which listen on ports 80 and 443

These ports are used to initiate a connection with RPC. 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. For more information about ports that RPC uses, visit the following Web site. For more information about how to disable CIS, see Microsoft Knowledge Base Article 825819.

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. •

Disable DCOM Disabling DCOM helps protect the affected system from remote attempts to exploit this vulnerability. However, the affected system could still be vulnerable to local elevation of privilege attacks that try to exploit this vulnerability. For instructions on how to disable DCOM, see Microsoft Knowledge Base Article 825750.

As an alternative to the steps that are documented In Microsoft Knowledge Base Article 825750, alternately you can paste the following text into a .reg file. Then, double-click the .reg file while you are logged on locally as an administrator:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole] "EnableDCOM"="N"

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.

Impact of Workaround: If you disable DCOM, you cannot use any DCOM dependant applications. Customers should evaluate whether any business critical applications rely on DCOM services before you deploy this workaround. There are potentially many built-in components and third-party applications that are affected if you disable DCOM. We do not recommend that you disable DCOM in your environment until you have tested to discover what applications are affected. Disabling DCOM may not be possible in all environments. Therefore, we recommend this workaround only on systems that cannot install the security update. For information about disabling DCOM, see Microsoft Knowledge Base Article 825750. Top of sectionTop of section

FAQ for COM+ Vulnerability - CAN-2005-1978:

What is the scope of the vulnerability? This is a remote code execution and local privilege elevation vulnerability. On Windows 2000 and Windows XP Service Pack 1, an anonymous attacker could remotely try to exploit this vulnerability. On Windows XP Service Pack 2, Windows Server 2003, and Windows Server 2003 Service Pack 1, this is strictly a local privilege elevation vulnerability because only an administrator can remotely access the affected component. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? The process that COM+ uses to create and use memory structures.

What is COM+? COM+ is the next step in the evolution of the Microsoft Component Object Model and Microsoft Transaction Server (MTS). COM+ handles resource management tasks, such as thread allocation and security. It automatically makes applications more scalable by providing thread pooling, object pooling, and just-in-time object activation. COM+ also helps protect the integrity of data by providing transaction support even if a transaction spans multiple databases over a network. For information about COM+, visit the following Microsoft Web site.

What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of the affected system.

Who could exploit the vulnerability? On Windows 2000 and Windows XP Service Pack 1, an anonymous 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 system to execute code. On Windows XP Service Pack 2, Windows Server 2003 and Windows Server 2003 Service Pack 1, an attacker must be able to log on locally to a system to try to exploit the vulnerability. If an attacker logged on locally to a system, the attacker could then run a specially crafted application to gain administrative privileges to that system.

What systems are primarily at risk from the vulnerability? Windows 2000 and Windows XP Service Pack 1 systems are primarily at risk from this vulnerability. The vulnerability could not be exploited remotely on Windows XP Service Pack 2, Windows Server 2003, and Windows Server 2003 Service Pack 1.

Could the vulnerability be exploited over the Internet? Yes, by anonymous users on Windows 2000 and Windows XP Service Pack 1. 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.

On Windows XP Service Pack 2, Windows Server 2003, and Windows Server 2003 Service Pack 1, an attacker must be able to log on to the specific system that is targeted for attack. An anonymous attacker cannot load and run a program remotely by using this vulnerability on these operating system versions.

What does the update do? The update removes the vulnerability by modifying the way that COM+ creates and uses internal memory structures.

When this security bulletin was issued, had this vulnerability been publicly disclosed? No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 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. Top of sectionTop of section Top of sectionTop of section

TIP Vulnerability - CAN-2005-1979:

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.

Mitigating Factors for TIP Vulnerability - CAN-2005-1979: •

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. •

On Windows XP Service Pack 1, Windows XP Service Pack 2, Windows Server 2003, and Windows Server 2003 Service Pack 1, even if the Microsoft Distributed Transaction Coordinator is started, the TIP protocol is not enabled. An administrator must manually enable the TIP protocol for the Distributed Transaction Coordinator to become vulnerable to this issue. •

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. Top of sectionTop of section

Workarounds for TIP Vulnerability - CAN-2005-1979:

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 in the following section. •

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

Step-by-Step Guide to Understanding the Group Policy Feature Set •

Windows 2000 Group Policy •

Group Policy in Windows Server 2003

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. •

Block TCP port 3372 at the firewall:

This port is used to initiate a connection with TIP. Blocking it 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 TIP ports 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. •

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. Top of sectionTop of section

FAQ for TIP Vulnerability - CAN-2005-1979:

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? The process that the Distributed Transaction Coordinator uses to validate TIP requests.

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 is TIP? MSDTC supports Transaction Internet Protocol (TIP). TIP transactions implicitly assume a two-pipe architecture. In this architecture, messages that describe the work flow on one pipe, the application-to-application pipe, and messages that control the transaction flow on another pipe, the transaction manager-to-transaction manager pipe. MS DTC selects TIP when an application program or resource manager explicitly uses the TIP COM interfaces. MS DTC also uses TIP when TIP is the only communication protocol that is common to both platforms. TIP is typically used when MS DTC is used in conjunction with transaction managers from other companies. For more information about TIP, visit the following Microsoft Web site. TIP is an IETF standard, documented at the following IETF Web site. For more information about security considerations that are associated with TIP, 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? When the TIP protocol is available, any anonymous user who could deliver a specially crafted network 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 TIP is enabled by default. If TIP is manually enabled on other operating system versions, they would be equally vulnerable to this issue.

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 MSDTC validates TIP requests.

When this security bulletin was issued, had this vulnerability been publicly disclosed? No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 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. Top of sectionTop of section Top of sectionTop of section

Distributed TIP Vulnerability - CAN-2005-1980:

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. This specially crafted message could also be transferred through the affected system to another TIP server. This distributed attack could cause the MSDTC on both systems to stop responding.

Mitigating Factors for Distributed TIP Vulnerability - CAN-2005-1980: •

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. •

On Windows XP Service Pack 1, Windows XP Service Pack 2, Windows Server 2003, and Windows Server 2003 Service Pack 1, even if the Microsoft Distributed Transaction Coordinator is started, the TIP protocol is not enabled. An administrator must manually enable the TIP protocol for the Distributed Transaction Coordinator to become vulnerable to this issue. •

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.

Top of sectionTop of section

Workarounds for Distributed TIP Vulnerability - CAN-2005-1980:

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 in the following section. •

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

Step-by-Step Guide to Understanding the Group Policy Feature Set •

Windows 2000 Group Policy •

Group Policy in Windows Server 2003

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. •

Block TCP port 3372 at the firewall:

This port is used to initiate a connection with TIP. Blocking it 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 TIP ports 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. •

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. Top of sectionTop of section

FAQ for Distributed TIP Vulnerability - CAN-2005-1980:

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. This specially crafted message could also be transferred through the affected system to another TIP server. This distributed attack could cause the MSDTC on both systems to stop responding. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights.

What causes the vulnerability? The process that the Distributed Transaction Coordinator uses to validate TIP requests.

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 is TIP? MSDTC supports Transaction Internet Protocol (TIP). TIP transactions implicitly assume a two-pipe architecture. In this architecture, messages that describe the work flow on one pipe, the application-to-application pipe, and messages that control the transaction flow on another pipe, the transaction manager-to-transaction manager pipe. MS DTC selects TIP when an application program or resource manager explicitly uses the TIP COM interfaces. MS DTC also uses TIP when TIP is the only communication protocol that is common to both platforms. TIP is typically used when MS DTC is used in conjunction with transaction managers from other companies. For more information about TIP, visit the following Microsoft Web site. TIP is an IETF standard, documented at the following IETF Web site. For more information about security considerations that are associated with TIP, 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 on the affected systems. This specially crafted message could also be transferred through the affected system to another TIP server and cause that systems MSDTC to stop responding.

Who could exploit the vulnerability? When the TIP protocol is available, any anonymous user who could deliver a specially crafted network 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.

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 TIP is enabled by default. If TIP is manually enabled on other operating system versions, they would be equally vulnerable to this issue.

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 MSDTC validates TIP requests.

When this security bulletin was issued, had this vulnerability been publicly disclosed? No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 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. Top of sectionTop of section Top of sectionTop of section Top of sectionTop of section

Security Update Information

Affected Software:

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

Windows Server 2003 (all versions)

Prerequisites This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.

Inclusion in Future Service Packs: The update for this issue will be included in 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 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-kb902400-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 KB902400.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-kb902400-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

You must restart your system after you apply this security update.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB902400$\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, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1: File Name Version Date Time Size CPU Folder

Catsrv.dll

2001.12.4720.374

21-Jul-2005

03:08

258,560

x86

RTMGDR

Catsrvut.dll

2001.12.4720.374

21-Jul-2005

03:08

584,192

x86

RTMGDR

Clbcatex.dll

2001.12.4720.374

21-Jul-2005

03:08

98,304

x86

RTMGDR

Clbcatq.dll

2001.12.4720.374

21-Jul-2005

03:08

489,984

x86

RTMGDR

Colbact.dll

2001.12.4720.374

21-Jul-2005

03:08

56,320

x86

RTMGDR

Comadmin.dll

2001.12.4720.374

21-Jul-2005

03:08

189,440

x86

RTMGDR

Comrepl.dll

2001.12.4720.374

21-Jul-2005

03:08

86,016

x86

RTMGDR

Comsvcs.dll

2001.12.4720.374

21-Jul-2005

03:08

1,202,176

x86

RTMGDR

Comuid.dll

2001.12.4720.374

21-Jul-2005

03:08

566,272

x86

RTMGDR

Es.dll

2001.12.4720.374

21-Jul-2005

03:08

226,816

x86

RTMGDR

Msdtcprx.dll

2001.12.4720.374

21-Jul-2005

03:08

443,904

x86

RTMGDR

Msdtctm.dll

2001.12.4720.397

26-Aug-2005

22:23

960,000

x86

RTMGDR

Msdtcuiu.dll

2001.12.4720.374

21-Jul-2005

03:08

160,768

x86

RTMGDR

Mtxclu.dll

2001.12.4720.374

21-Jul-2005

03:08

76,288

x86

RTMGDR

Mtxdm.dll

2001.12.4720.374

21-Jul-2005

03:08

18,944

x86

RTMGDR

Mtxoci.dll

2001.12.4720.374

21-Jul-2005

03:08

108,032

x86

RTMGDR

Ole32.dll

5.2.3790.374

21-Jul-2005

03:08

1,192,448

x86

RTMGDR

Olecli32.dll

5.2.3790.374

21-Jul-2005

03:08

72,192

x86

RTMGDR

Olecnv32.dll

5.2.3790.374

21-Jul-2005

03:08

36,352

x86

RTMGDR

Rpcproxy.dll

5.2.3790.137

16-Mar-2004

03:09

26,112

x86

RTMGDR

Rpcrt4.dll

5.2.3790.137

16-Mar-2004

03:09

660,992

x86

RTMGDR

Rpcss.dll

5.2.3790.374

21-Jul-2005

03:08

295,936

x86

RTMGDR

Stclient.dll

2001.12.4720.374

21-Jul-2005

03:08

60,416

x86

RTMGDR

Txflog.dll

2001.12.4720.374

21-Jul-2005

03:08

94,720

x86

RTMGDR

Catsrv.dll

2001.12.4720.374

21-Jul-2005

03:12

258,560

x86

RTMQFE

Catsrvut.dll

2001.12.4720.374

26-Aug-2005

23:37

584,704

x86

RTMQFE

Clbcatex.dll

2001.12.4720.374

21-Jul-2005

03:12

98,304

x86

RTMQFE

Clbcatq.dll

2001.12.4720.374

21-Jul-2005

03:12

490,496

x86

RTMQFE

Colbact.dll

2001.12.4720.374

21-Jul-2005

03:12

56,320

x86

RTMQFE

Comadmin.dll

2001.12.4720.374

21-Jul-2005

03:12

189,440

x86

RTMQFE

Comrepl.dll

2001.12.4720.374

21-Jul-2005

03:12

86,528

x86

RTMQFE

Comsvcs.dll

2001.12.4720.397

26-Aug-2005

22:25

1,207,296

x86

RTMQFE

Comuid.dll

2001.12.4720.374

21-Jul-2005

03:12

566,272

x86

RTMQFE

Es.dll

2001.12.4720.374

21-Jul-2005

03:12

226,816

x86

RTMQFE

Msdtcprx.dll

2001.12.4720.374

21-Jul-2005

03:12

446,464

x86

RTMQFE

Msdtctm.dll

2001.12.4720.397

26-Aug-2005

22:25

962,048

x86

RTMQFE

Msdtcuiu.dll

2001.12.4720.374

21-Jul-2005

03:12

161,280

x86

RTMQFE

Mtxclu.dll

2001.12.4720.374

21-Jul-2005

03:12

76,288

x86

RTMQFE

Mtxdm.dll

2001.12.4720.374

21-Jul-2005

03:12

18,944

x86

RTMQFE

Mtxoci.dll

2001.12.4720.374

21-Jul-2005

03:12

109,056

x86

RTMQFE

Ole32.dll

5.2.3790.374

21-Jul-2005

03:12

1,193,984

x86

RTMQFE

Olecli32.dll

5.2.3790.374

21-Jul-2005

03:12

72,192

x86

RTMQFE

Olecnv32.dll

5.2.3790.374

21-Jul-2005

03:12

36,352

x86

RTMQFE

Rpcproxy.dll

5.2.3790.141

16-Mar-2004

03:17

26,112

x86

RTMQFE

Rpcrt4.dll

5.2.3790.141

16-Mar-2004

03:17

659,968

x86

RTMQFE

Rpcss.dll

5.2.3790.374

21-Jul-2005

03:12

296,960

x86

RTMQFE

Stclient.dll

2001.12.4720.374

21-Jul-2005

03:12

60,416

x86

RTMQFE

Txflog.dll

2001.12.4720.374

21-Jul-2005

03:12

94,720

x86

RTMQFE

Catsrv.dll

2001.12.4720.2492

21-Jul-2005

03:24

274,432

x86

SP1GDR

Catsrvut.dll

2001.12.4720.2492

21-Jul-2005

03:24

619,520

x86

SP1GDR

Clbcatex.dll

2001.12.4720.2492

21-Jul-2005

03:24

104,960

x86

SP1GDR

Clbcatq.dll

2001.12.4720.2492

21-Jul-2005

03:24

512,000

x86

SP1GDR

Colbact.dll

2001.12.4720.2492

21-Jul-2005

03:24

58,880

x86

SP1GDR

Comadmin.dll

2001.12.4720.2492

21-Jul-2005

03:24

196,608

x86

SP1GDR

Comrepl.dll

2001.12.4720.2492

21-Jul-2005

03:24

88,576

x86

SP1GDR

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

22:18

1,247,744

x86

SP1GDR

Comuid.dll

2001.12.4720.2492

21-Jul-2005

03:24

596,480

x86

SP1GDR

Es.dll

2001.12.4720.2492

21-Jul-2005

03:24

238,592

x86

SP1GDR

Msdtcprx.dll

2001.12.4720.2492

21-Jul-2005

03:24

466,432

x86

SP1GDR

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

22:18

996,352

x86

SP1GDR

Msdtcuiu.dll

2001.12.4720.2492

21-Jul-2005

03:24

165,888

x86

SP1GDR

Mtxclu.dll

2001.12.4720.2492

21-Jul-2005

03:24

78,848

x86

SP1GDR

Mtxdm.dll

2001.12.4720.2492

21-Jul-2005

03:24

20,992

x86

SP1GDR

Mtxoci.dll

2001.12.4720.2492

21-Jul-2005

03:24

111,104

x86

SP1GDR

Ole32.dll

5.2.3790.2492

21-Jul-2005

03:24

1,245,184

x86

SP1GDR

Olecli32.dll

5.2.3790.2492

21-Jul-2005

03:24

75,776

SP1GDR

Olecnv32.dll

5.2.3790.2492

21-Jul-2005

03:24

38,912

x86

SP1GDR

Rpcss.dll

5.2.3790.2492

21-Jul-2005

03:24

417,792

x86

SP1GDR

Stclient.dll

2001.12.4720.2492

21-Jul-2005

03:24

64,000

x86

SP1GDR

Txflog.dll

2001.12.4720.2492

21-Jul-2005

03:24

98,816

x86

SP1GDR

Catsrv.dll

2001.12.4720.2492

21-Jul-2005

03:37

274,432

x86

SP1QFE

Catsrvut.dll

2001.12.4720.2492

21-Jul-2005

03:37

619,520

x86

SP1QFE

Clbcatex.dll

2001.12.4720.2492

21-Jul-2005

03:37

104,960

x86

SP1QFE

Clbcatq.dll

2001.12.4720.2492

21-Jul-2005

03:37

514,048

x86

SP1QFE

Colbact.dll

2001.12.4720.2492

21-Jul-2005

03:37

58,880

x86

SP1QFE

Comadmin.dll

2001.12.4720.2492

21-Jul-2005

03:37

196,608

x86

SP1QFE

Comrepl.dll

2001.12.4720.2492

21-Jul-2005

03:37

88,576

x86

SP1QFE

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:40

1,267,712

x86

SP1QFE

Comuid.dll

2001.12.4720.2492

21-Jul-2005

03:37

596,480

x86

SP1QFE

Es.dll

2001.12.4720.2492

21-Jul-2005

03:37

238,592

x86

SP1QFE

Msdtcprx.dll

2001.12.4720.2492

21-Jul-2005

03:37

466,944

x86

SP1QFE

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

22:20

998,400

x86

SP1QFE

Msdtcuiu.dll

2001.12.4720.2492

21-Jul-2005

03:37

165,888

x86

SP1QFE

Mtxclu.dll

2001.12.4720.2492

21-Jul-2005

03:37

78,848

x86

SP1QFE

Mtxdm.dll

2001.12.4720.2492

21-Jul-2005

03:37

20,992

x86

SP1QFE

Mtxoci.dll

2001.12.4720.2492

21-Jul-2005

03:37

111,104

x86

SP1QFE

Ole32.dll

5.2.3790.2492

21-Jul-2005

03:37

1,245,696

x86

SP1QFE

Olecli32.dll

5.2.3790.2492

21-Jul-2005

03:37

75,776

SP1QFE

Olecnv32.dll

5.2.3790.2492

21-Jul-2005

03:37

38,912

x86

SP1QFE

Rpcss.dll

5.2.3790.2492

21-Jul-2005

03:37

418,304

x86

SP1QFE

Stclient.dll

2001.12.4720.2492

21-Jul-2005

03:37

64,000

x86

SP1QFE

Txflog.dll

2001.12.4720.2492

21-Jul-2005

03:37

98,816

x86

SP1QFE

Arpidfix.exe

5.2.3790.2517

26-Aug-2005

01:42

32,256

x86

Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems: File Name Version Date Time Size CPU Folder

Catsrv.dll

2001.12.4720.374

30-Aug-2005

00:50

621,568

IA-64

RTMGDR

Catsrvut.dll

2001.12.4720.374

30-Aug-2005

00:50

1,554,944

IA-64

RTMGDR

Clbcatex.dll

2001.12.4720.374

30-Aug-2005

00:50

263,680

IA-64

RTMGDR

Clbcatq.dll

2001.12.4720.374

30-Aug-2005

00:50

1,286,656

IA-64

RTMGDR

Colbact.dll

2001.12.4720.374

30-Aug-2005

00:50

170,496

IA-64

RTMGDR

Comadmin.dll

2001.12.4720.374

30-Aug-2005

00:50

411,136

IA-64

RTMGDR

Comrepl.dll

2001.12.4720.374

30-Aug-2005

00:50

273,920

IA-64

RTMGDR

Comsvcs.dll

2001.12.4720.374

30-Aug-2005

00:50

3,128,320

IA-64

RTMGDR

Comuid.dll

2001.12.4720.374

30-Aug-2005

00:50

1,873,408

IA-64

RTMGDR

Es.dll

2001.12.4720.374

30-Aug-2005

00:50

653,312

IA-64

RTMGDR

Msdtcprx.dll

2001.12.4720.374

30-Aug-2005

00:50

1,301,504

IA-64

RTMGDR

Msdtctm.dll

2001.12.4720.398

30-Aug-2005

00:50

3,145,728

IA-64

RTMGDR

Msdtcuiu.dll

2001.12.4720.374

30-Aug-2005

00:50

462,848

IA-64

RTMGDR

Mtxclu.dll

2001.12.4720.374

30-Aug-2005

00:50

203,776

IA-64

RTMGDR

Mtxdm.dll

2001.12.4720.374

30-Aug-2005

00:50

45,056

IA-64

RTMGDR

Mtxoci.dll

2001.12.4720.374

30-Aug-2005

00:50

315,904

IA-64

RTMGDR

Ole32.dll

5.2.3790.374

30-Aug-2005

00:50

3,577,856

IA-64

RTMGDR

Olecli32.dll

5.2.3790.374

30-Aug-2005

00:50

223,744

IA-64

RTMGDR

Olecnv32.dll

5.2.3790.374

30-Aug-2005

00:50

89,088

IA-64

RTMGDR

Rpcproxy.dll

5.2.3790.137

30-Aug-2005

00:50

73,216

IA-64

RTMGDR

Rpcrt4.dll

5.2.3790.137

30-Aug-2005

00:50

2,140,160

IA-64

RTMGDR

Rpcss.dll

5.2.3790.374

30-Aug-2005

00:50

691,200

IA-64

RTMGDR

Stclient.dll

2001.12.4720.374

30-Aug-2005

00:50

140,800

IA-64

RTMGDR

Txflog.dll

2001.12.4720.374

30-Aug-2005

00:50

279,552

IA-64

RTMGDR

Wcatsrv.dll

2001.12.4720.374

30-Aug-2005

00:50

258,560

x86

RTMGDR\WOW

Wcatsrvut.dll

2001.12.4720.374

30-Aug-2005

00:50

584,192

x86

RTMGDR\WOW

Wclbcatex.dll

2001.12.4720.374

30-Aug-2005

00:50

98,304

x86

RTMGDR\WOW

Wclbcatq.dll

2001.12.4720.374

30-Aug-2005

00:50

489,984

x86

RTMGDR\WOW

Wcolbact.dll

2001.12.4720.374

30-Aug-2005

00:50

56,320

x86

RTMGDR\WOW

Wcomadmin.dll

2001.12.4720.374

30-Aug-2005

00:50

189,440

x86

RTMGDR\WOW

Wcomsvcs.dll

2001.12.4720.374

30-Aug-2005

00:50

1,202,176

x86

RTMGDR\WOW

Wes.dll

2001.12.4720.374

30-Aug-2005

00:50

226,816

x86

RTMGDR\WOW

Wmsdtcprx.dll

2001.12.4720.374

30-Aug-2005

00:50

443,904

x86

RTMGDR\WOW

Wmsdtcuiu.dll

2001.12.4720.374

30-Aug-2005

00:50

160,768

x86

RTMGDR\WOW

Wmtxclu.dll

2001.12.4720.374

30-Aug-2005

00:50

76,288

x86

RTMGDR\WOW

Wmtxdm.dll

2001.12.4720.374

30-Aug-2005

00:50

18,944

x86

RTMGDR\WOW

Wmtxoci.dll

2001.12.4720.374

30-Aug-2005

00:50

108,032

x86

RTMGDR\WOW

Wole32.dll

5.2.3790.374

30-Aug-2005

00:50

1,192,448

x86

RTMGDR\WOW

Wolecli32.dll

5.2.3790.374

30-Aug-2005

00:50

72,192

x86

RTMGDR\WOW

Wolecnv32.dll

5.2.3790.374

30-Aug-2005

00:50

36,352

x86

RTMGDR\WOW

Wrpcproxy.dll

5.2.3790.137

30-Aug-2005

00:50

26,112

x86

RTMGDR\WOW

Wrpcrt4.dll

5.2.3790.137

30-Aug-2005

00:50

542,208

x86

RTMGDR\WOW

Wstclient.dll

2001.12.4720.374

30-Aug-2005

00:50

60,416

x86

RTMGDR\WOW

Wtxflog.dll

2001.12.4720.374

30-Aug-2005

00:50

94,720

x86

RTMGDR\WOW

Catsrv.dll

2001.12.4720.374

30-Aug-2005

00:51

622,080

IA-64

RTMQFE

Catsrvut.dll

2001.12.4720.374

30-Aug-2005

00:51

1,555,456

IA-64

RTMQFE

Clbcatex.dll

2001.12.4720.374

30-Aug-2005

00:51

263,680

IA-64

RTMQFE

Clbcatq.dll

2001.12.4720.374

30-Aug-2005

00:51

1,287,168

IA-64

RTMQFE

Colbact.dll

2001.12.4720.374

30-Aug-2005

00:51

171,008

IA-64

RTMQFE

Comadmin.dll

2001.12.4720.374

30-Aug-2005

00:51

411,136

IA-64

RTMQFE

Comrepl.dll

2001.12.4720.374

30-Aug-2005

00:51

275,456

IA-64

RTMQFE

Comsvcs.dll

2001.12.4720.398

30-Aug-2005

00:51

3,143,168

IA-64

RTMQFE

Comuid.dll

2001.12.4720.374

30-Aug-2005

00:51

1,873,408

IA-64

RTMQFE

Es.dll

2001.12.4720.374

30-Aug-2005

00:51

654,336

IA-64

RTMQFE

Msdtcprx.dll

2001.12.4720.374

30-Aug-2005

00:51

1,311,744

IA-64

RTMQFE

Msdtctm.dll

2001.12.4720.398

30-Aug-2005

00:51

3,152,384

IA-64

RTMQFE

Msdtcuiu.dll

2001.12.4720.374

30-Aug-2005

00:51

463,360

IA-64

RTMQFE

Mtxclu.dll

2001.12.4720.374

30-Aug-2005

00:51

203,776

IA-64

RTMQFE

Mtxdm.dll

2001.12.4720.374

30-Aug-2005

00:51

45,568

IA-64

RTMQFE

Mtxoci.dll

2001.12.4720.374

30-Aug-2005

00:51

320,000

IA-64

RTMQFE

Ole32.dll

5.2.3790.374

30-Aug-2005

00:51

3,582,976

IA-64

RTMQFE

Olecli32.dll

5.2.3790.374

30-Aug-2005

00:51

223,744

IA-64

RTMQFE

Olecnv32.dll

5.2.3790.374

30-Aug-2005

00:51

89,088

IA-64

RTMQFE

Rpcproxy.dll

5.2.3790.141

30-Aug-2005

00:51

73,216

IA-64

RTMQFE

Rpcrt4.dll

5.2.3790.141

30-Aug-2005

00:51

2,150,400

IA-64

RTMQFE

Rpcss.dll

5.2.3790.374

30-Aug-2005

00:51

694,272

IA-64

RTMQFE

Stclient.dll

2001.12.4720.374

30-Aug-2005

00:51

140,800

IA-64

RTMQFE

Txflog.dll

2001.12.4720.374

30-Aug-2005

00:51

280,064

IA-64

RTMQFE

Wcatsrv.dll

2001.12.4720.374

30-Aug-2005

00:51

258,560

x86

RTMQFE\WOW

Wcatsrvut.dll

2001.12.4720.374

30-Aug-2005

00:51

584,704

x86

RTMQFE\WOW

Wclbcatex.dll

2001.12.4720.374

30-Aug-2005

00:51

98,304

x86

RTMQFE\WOW

Wclbcatq.dll

2001.12.4720.374

30-Aug-2005

00:51

490,496

x86

RTMQFE\WOW

Wcolbact.dll

2001.12.4720.374

30-Aug-2005

00:51

56,320

x86

RTMQFE\WOW

Wcomadmin.dll

2001.12.4720.374

30-Aug-2005

00:51

189,440

x86

RTMQFE\WOW

Wcomsvcs.dll

2001.12.4720.398

30-Aug-2005

00:51

1,207,296

x86

RTMQFE\WOW

Wes.dll

2001.12.4720.374

30-Aug-2005

00:51

226,816

x86

RTMQFE\WOW

Wmsdtcprx.dll

2001.12.4720.374

30-Aug-2005

00:51

446,464

x86

RTMQFE\WOW

Wmsdtcuiu.dll

2001.12.4720.374

30-Aug-2005

00:51

161,280

x86

RTMQFE\WOW

Wmtxclu.dll

2001.12.4720.374

30-Aug-2005

00:51

76,288

x86

RTMQFE\WOW

Wmtxdm.dll

2001.12.4720.374

30-Aug-2005

00:51

18,944

x86

RTMQFE\WOW

Wmtxoci.dll

2001.12.4720.374

30-Aug-2005

00:51

109,056

x86

RTMQFE\WOW

Wole32.dll

5.2.3790.374

30-Aug-2005

00:51

1,193,984

x86

RTMQFE\WOW

Wolecli32.dll

5.2.3790.374

30-Aug-2005

00:51

72,192

x86

RTMQFE\WOW

Wolecnv32.dll

5.2.3790.374

30-Aug-2005

00:51

36,352

x86

RTMQFE\WOW

Wrpcproxy.dll

5.2.3790.141

30-Aug-2005

00:51

26,112

x86

RTMQFE\WOW

Wrpcrt4.dll

5.2.3790.141

30-Aug-2005

00:51

544,256

x86

RTMQFE\WOW

Wstclient.dll

2001.12.4720.374

30-Aug-2005

00:51

60,416

x86

RTMQFE\WOW

Wtxflog.dll

2001.12.4720.374

30-Aug-2005

00:51

94,720

x86

RTMQFE\WOW

Catsrv.dll

2001.12.4720.2492

30-Aug-2005

00:48

657,920

IA-64

SP1GDR

Catsrvut.dll

2001.12.4720.2492

30-Aug-2005

00:48

1,632,256

IA-64

SP1GDR

Clbcatex.dll

2001.12.4720.2492

30-Aug-2005

00:48

279,040

IA-64

SP1GDR

Clbcatq.dll

2001.12.4720.2492

30-Aug-2005

00:48

1,351,680

IA-64

SP1GDR

Colbact.dll

2001.12.4720.2492

30-Aug-2005

00:48

181,248

IA-64

SP1GDR

Comadmin.dll

2001.12.4720.2492

30-Aug-2005

00:48

420,352

IA-64

SP1GDR

Comrepl.dll

2001.12.4720.2492

30-Aug-2005

00:48

285,184

IA-64

SP1GDR

Comsvcs.dll

2001.12.4720.2518

30-Aug-2005

00:48

3,299,840

IA-64

SP1GDR

Comuid.dll

2001.12.4720.2492

30-Aug-2005

00:48

1,978,880

IA-64

SP1GDR

Es.dll

2001.12.4720.2492

30-Aug-2005

00:48

701,952

IA-64

SP1GDR

Msdtcprx.dll

2001.12.4720.2492

30-Aug-2005

00:48

1,329,152

IA-64

SP1GDR

Msdtctm.dll

2001.12.4720.2518

30-Aug-2005

00:48

3,059,712

IA-64

SP1GDR

Msdtcuiu.dll

2001.12.4720.2492

30-Aug-2005

00:48

486,400

IA-64

SP1GDR

Mtxclu.dll

2001.12.4720.2492

30-Aug-2005

00:48

207,872

IA-64

SP1GDR

Mtxdm.dll

2001.12.4720.2492

30-Aug-2005

00:48

48,128

IA-64

SP1GDR

Mtxoci.dll

2001.12.4720.2492

30-Aug-2005

00:48

322,048

IA-64

SP1GDR

Ole32.dll

5.2.3790.2492

30-Aug-2005

00:48

3,992,064

IA-64

SP1GDR

Olecli32.dll

5.2.3790.2492

30-Aug-2005

00:48

252,416

IA-64

SP1GDR

Olecnv32.dll

5.2.3790.2492

30-Aug-2005

00:48

90,112

IA-64

SP1GDR

Rpcss.dll

5.2.3790.2492

30-Aug-2005

00:48

847,872

IA-64

SP1GDR

Stclient.dll

2001.12.4720.2492

30-Aug-2005

00:48

149,504

IA-64

SP1GDR

Txflog.dll

2001.12.4720.2492

30-Aug-2005

00:48

303,104

IA-64

SP1GDR

Wcatsrv.dll

2001.12.4720.2492

30-Aug-2005

00:48

274,432

x86

SP1GDR\WOW

Wcatsrvut.dll

2001.12.4720.2492

30-Aug-2005

00:48

619,520

x86

SP1GDR\WOW

Wclbcatex.dll

2001.12.4720.2492

30-Aug-2005

00:48

104,960

x86

SP1GDR\WOW

Wclbcatq.dll

2001.12.4720.2492

30-Aug-2005

00:48

512,000

x86

SP1GDR\WOW

Wcolbact.dll

2001.12.4720.2492

30-Aug-2005

00:48

58,880

x86

SP1GDR\WOW

Wcomadmin.dll

2001.12.4720.2492

30-Aug-2005

00:48

196,608

x86

SP1GDR\WOW

Wcomsvcs.dll

2001.12.4720.2517

30-Aug-2005

00:48

1,247,744

x86

SP1GDR\WOW

Wcomuid.dll

2001.12.4720.2492

30-Aug-2005

00:48

596,480

x86

SP1GDR\WOW

Wes.dll

2001.12.4720.2492

30-Aug-2005

00:48

238,592

x86

SP1GDR\WOW

Wmsdtcprx.dll

2001.12.4720.2492

30-Aug-2005

00:48

466,432

x86

SP1GDR\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

30-Aug-2005

00:48

165,888

x86

SP1GDR\WOW

Wmtxclu.dll

2001.12.4720.2492

30-Aug-2005

00:48

78,848

x86

SP1GDR\WOW

Wmtxdm.dll

2001.12.4720.2492

30-Aug-2005

00:48

20,992

x86

SP1GDR\WOW

Wmtxoci.dll

2001.12.4720.2492

30-Aug-2005

00:48

111,104

x86

SP1GDR\WOW

Wole32.dll

5.2.3790.2492

30-Aug-2005

00:48

1,245,184

x86

SP1GDR\WOW

Wolecli32.dll

5.2.3790.2492

30-Aug-2005

00:48

75,776

SP1GDR\WOW

Wolecnv32.dll

5.2.3790.2492

30-Aug-2005

00:48

38,912

x86

SP1GDR\WOW

Wstclient.dll

2001.12.4720.2492

30-Aug-2005

00:48

64,000

x86

SP1GDR\WOW

Wtxflog.dll

2001.12.4720.2492

30-Aug-2005

00:48

98,816

x86

SP1GDR\WOW

Catsrv.dll

2001.12.4720.2492

30-Aug-2005

00:53

657,920

IA-64

SP1QFE

Catsrvut.dll

2001.12.4720.2492

30-Aug-2005

00:53

1,632,256

IA-64

SP1QFE

Clbcatex.dll

2001.12.4720.2492

30-Aug-2005

00:53

279,040

IA-64

SP1QFE

Clbcatq.dll

2001.12.4720.2492

30-Aug-2005

00:53

1,354,752

IA-64

SP1QFE

Colbact.dll

2001.12.4720.2492

30-Aug-2005

00:53

181,760

IA-64

SP1QFE

Comadmin.dll

2001.12.4720.2492

30-Aug-2005

00:53

420,352

IA-64

SP1QFE

Comrepl.dll

2001.12.4720.2492

30-Aug-2005

00:53

285,184

IA-64

SP1QFE

Comsvcs.dll

2001.12.4720.2518

30-Aug-2005

00:53

3,365,888

IA-64

SP1QFE

Comuid.dll

2001.12.4720.2492

30-Aug-2005

00:53

1,978,880

IA-64

SP1QFE

Es.dll

2001.12.4720.2492

30-Aug-2005

00:53

701,440

IA-64

SP1QFE

Msdtcprx.dll

2001.12.4720.2492

30-Aug-2005

00:53

1,330,176

IA-64

SP1QFE

Msdtctm.dll

2001.12.4720.2518

30-Aug-2005

00:53

3,065,856

IA-64

SP1QFE

Msdtcuiu.dll

2001.12.4720.2492

30-Aug-2005

00:53

486,400

IA-64

SP1QFE

Mtxclu.dll

2001.12.4720.2492

30-Aug-2005

00:53

207,872

IA-64

SP1QFE

Mtxdm.dll

2001.12.4720.2492

30-Aug-2005

00:53

47,616

IA-64

SP1QFE

Mtxoci.dll

2001.12.4720.2492

30-Aug-2005

00:53

322,048

IA-64

SP1QFE

Ole32.dll

5.2.3790.2492

30-Aug-2005

00:53

3,995,648

IA-64

SP1QFE

Olecli32.dll

5.2.3790.2492

30-Aug-2005

00:53

252,416

IA-64

SP1QFE

Olecnv32.dll

5.2.3790.2492

30-Aug-2005

00:53

90,112

IA-64

SP1QFE

Rpcss.dll

5.2.3790.2492

30-Aug-2005

00:53

849,408

IA-64

SP1QFE

Stclient.dll

2001.12.4720.2492

30-Aug-2005

00:53

149,504

IA-64

SP1QFE

Txflog.dll

2001.12.4720.2492

30-Aug-2005

00:53

303,104

IA-64

SP1QFE

Wcatsrv.dll

2001.12.4720.2492

30-Aug-2005

00:53

274,432

x86

SP1QFE\WOW

Wcatsrvut.dll

2001.12.4720.2492

30-Aug-2005

00:53

619,520

x86

SP1QFE\WOW

Wclbcatex.dll

2001.12.4720.2492

30-Aug-2005

00:53

104,960

x86

SP1QFE\WOW

Wclbcatq.dll

2001.12.4720.2492

30-Aug-2005

00:53

514,048

x86

SP1QFE\WOW

Wcolbact.dll

2001.12.4720.2492

30-Aug-2005

00:53

58,880

x86

SP1QFE\WOW

Wcomadmin.dll

2001.12.4720.2492

30-Aug-2005

00:53

196,608

x86

SP1QFE\WOW

Wcomsvcs.dll

2001.12.4720.2518

30-Aug-2005

00:53

1,267,712

x86

SP1QFE\WOW

Wcomuid.dll

2001.12.4720.2492

30-Aug-2005

00:53

596,480

x86

SP1QFE\WOW

Wes.dll

2001.12.4720.2492

30-Aug-2005

00:53

238,592

x86

SP1QFE\WOW

Wmsdtcprx.dll

2001.12.4720.2492

30-Aug-2005

00:53

466,944

x86

SP1QFE\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

30-Aug-2005

00:53

165,888

x86

SP1QFE\WOW

Wmtxclu.dll

2001.12.4720.2492

30-Aug-2005

00:53

78,848

x86

SP1QFE\WOW

Wmtxdm.dll

2001.12.4720.2492

30-Aug-2005

00:53

20,992

x86

SP1QFE\WOW

Wmtxoci.dll

2001.12.4720.2492

30-Aug-2005

00:53

111,104

x86

SP1QFE\WOW

Wole32.dll

5.2.3790.2492

30-Aug-2005

00:53

1,245,696

x86

SP1QFE\WOW

Wolecli32.dll

5.2.3790.2492

30-Aug-2005

00:53

75,776

SP1QFE\WOW

Wolecnv32.dll

5.2.3790.2492

30-Aug-2005

00:53

38,912

x86

SP1QFE\WOW

Wstclient.dll

2001.12.4720.2492

30-Aug-2005

00:53

64,000

x86

SP1QFE\WOW

Wtxflog.dll

2001.12.4720.2492

30-Aug-2005

00:53

98,816

x86

SP1QFE\WOW

Arpidfix.exe

5.2.3790.2518

30-Aug-2005

00:54

74,752

IA-64

Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition: File Name Version Date Time Size CPU Folder

Catsrv.dll

2001.12.4720.2492

26-Aug-2005

23:43

418,816

x64

SP1GDR

Catsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:43

1,084,416

x64

SP1GDR

Clbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:43

175,104

x64

SP1GDR

Clbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:43

880,128

x64

SP1GDR

Colbact.dll

2001.12.4720.2492

26-Aug-2005

23:43

97,792

x64

SP1GDR

Comadmin.dll

2001.12.4720.2492

26-Aug-2005

23:43

288,768

x64

SP1GDR

Comrepl.dll

2001.12.4720.2492

26-Aug-2005

23:43

188,928

x64

SP1GDR

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:43

2,156,544

x64

SP1GDR

Comuid.dll

2001.12.4720.2492

26-Aug-2005

23:43

1,478,144

x64

SP1GDR

Es.dll

2001.12.4720.2492

26-Aug-2005

23:43

365,568

x64

SP1GDR

Msdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:43

824,320

x64

SP1GDR

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

23:43

2,052,096

x64

SP1GDR

Msdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:43

291,328

x64

SP1GDR

Mtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:43

144,896

x64

SP1GDR

Mtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:43

30,720

x64

SP1GDR

Mtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:43

175,104

x64

SP1GDR

Ole32.dll

5.2.3790.2492

26-Aug-2005

23:43

2,543,104

x64

SP1GDR

Olecli32.dll

5.2.3790.2492

26-Aug-2005

23:43

131,584

x64

SP1GDR

Olecnv32.dll

5.2.3790.2492

26-Aug-2005

23:43

56,832

x64

SP1GDR

Rpcss.dll

5.2.3790.2492

26-Aug-2005

23:43

691,200

x64

SP1GDR

Stclient.dll

2001.12.4720.2492

26-Aug-2005

23:43

101,888

x64

SP1GDR

Txflog.dll

2001.12.4720.2492

26-Aug-2005

23:43

179,200

x64

SP1GDR

Wcatsrv.dll

2001.12.4720.2492

26-Aug-2005

23:43

274,432

x86

SP1GDR\WOW

Wcatsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:43

619,520

x86

SP1GDR\WOW

Wclbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:43

104,960

x86

SP1GDR\WOW

Wclbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:43

512,000

x86

SP1GDR\WOW

Wcolbact.dll

2001.12.4720.2492

26-Aug-2005

23:43

58,880

x86

SP1GDR\WOW

Wcomadmin.dll

2001.12.4720.2492

26-Aug-2005

23:43

196,608

x86

SP1GDR\WOW

Wcomsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:43

1,247,744

x86

SP1GDR\WOW

Wcomuid.dll

2001.12.4720.2492

26-Aug-2005

23:43

596,480

x86

SP1GDR\WOW

Wes.dll

2001.12.4720.2492

26-Aug-2005

23:43

238,592

x86

SP1GDR\WOW

Wmsdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:43

466,432

x86

SP1GDR\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:43

165,888

x86

SP1GDR\WOW

Wmtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:43

78,848

x86

SP1GDR\WOW

Wmtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:43

20,992

x86

SP1GDR\WOW

Wmtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:43

111,104

x86

SP1GDR\WOW

Wole32.dll

5.2.3790.2492

26-Aug-2005

23:43

1,245,184

x86

SP1GDR\WOW

Wolecli32.dll

5.2.3790.2492

26-Aug-2005

23:43

75,776

SP1GDR\WOW

Wolecnv32.dll

5.2.3790.2492

26-Aug-2005

23:43

38,912

x86

SP1GDR\WOW

Wstclient.dll

2001.12.4720.2492

26-Aug-2005

23:43

64,000

x86

SP1GDR\WOW

Wtxflog.dll

2001.12.4720.2492

26-Aug-2005

23:43

98,816

x86

SP1GDR\WOW

Catsrv.dll

2001.12.4720.2492

26-Aug-2005

23:47

418,304

x64

SP1QFE

Catsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:47

1,084,416

x64

SP1QFE

Clbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:47

175,104

x64

SP1QFE

Clbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:47

882,176

x64

SP1QFE

Colbact.dll

2001.12.4720.2492

26-Aug-2005

23:47

97,280

x64

SP1QFE

Comadmin.dll

2001.12.4720.2492

26-Aug-2005

23:47

288,768

x64

SP1QFE

Comrepl.dll

2001.12.4720.2492

26-Aug-2005

23:47

188,928

x64

SP1QFE

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:47

2,191,872

x64

SP1QFE

Comuid.dll

2001.12.4720.2492

26-Aug-2005

23:47

1,478,144

x64

SP1QFE

Es.dll

2001.12.4720.2492

26-Aug-2005

23:47

365,568

x64

SP1QFE

Msdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:47

825,344

x64

SP1QFE

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

23:47

2,053,120

x64

SP1QFE

Msdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:47

291,328

x64

SP1QFE

Mtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:47

144,896

x64

SP1QFE

Mtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:47

30,208

x64

SP1QFE

Mtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:47

175,104

x64

SP1QFE

Ole32.dll

5.2.3790.2492

26-Aug-2005

23:47

2,544,640

x64

SP1QFE

Olecli32.dll

5.2.3790.2492

26-Aug-2005

23:47

131,584

x64

SP1QFE

Olecnv32.dll

5.2.3790.2492

26-Aug-2005

23:47

56,832

x64

SP1QFE

Rpcss.dll

5.2.3790.2492

26-Aug-2005

23:47

692,224

x64

SP1QFE

Stclient.dll

2001.12.4720.2492

26-Aug-2005

23:47

101,888

x64

SP1QFE

Txflog.dll

2001.12.4720.2492

26-Aug-2005

23:47

179,200

x64

SP1QFE

Wcatsrv.dll

2001.12.4720.2492

26-Aug-2005

23:47

274,432

x86

SP1QFE\WOW

Wcatsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:47

619,520

x86

SP1QFE\WOW

Wclbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:47

104,960

x86

SP1QFE\WOW

Wclbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:47

514,048

x86

SP1QFE\WOW

Wcolbact.dll

2001.12.4720.2492

26-Aug-2005

23:47

58,880

x86

SP1QFE\WOW

Wcomadmin.dll

2001.12.4720.2492

26-Aug-2005

23:47

196,608

x86

SP1QFE\WOW

Wcomsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:47

1,267,712

x86

SP1QFE\WOW

Wcomuid.dll

2001.12.4720.2492

26-Aug-2005

23:47

596,480

x86

SP1QFE\WOW

Wes.dll

2001.12.4720.2492

26-Aug-2005

23:47

238,592

x86

SP1QFE\WOW

Wmsdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:47

466,944

x86

SP1QFE\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:47

165,888

x86

SP1QFE\WOW

Wmtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:47

78,848

x86

SP1QFE\WOW

Wmtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:47

20,992

x86

SP1QFE\WOW

Wmtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:47

111,104

x86

SP1QFE\WOW

Wole32.dll

5.2.3790.2492

26-Aug-2005

23:47

1,245,696

x86

SP1QFE\WOW

Wolecli32.dll

5.2.3790.2492

26-Aug-2005

23:47

75,776

SP1QFE\WOW

Wolecnv32.dll

5.2.3790.2492

26-Aug-2005

23:47

38,912

x86

SP1QFE\WOW

Wstclient.dll

2001.12.4720.2492

26-Aug-2005

23:47

64,000

x86

SP1QFE\WOW

Wtxflog.dll

2001.12.4720.2492

26-Aug-2005

23:47

98,816

x86

SP1QFE\WOW

Arpidfix.exe

5.2.3790.2517

26-Aug-2005

23:49

43,008

x64

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

Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.

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, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB902400\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 902400 security update into the Windows installation source files. Top of sectionTop of section

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-kb902400-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 KB902400.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-kb902400-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

You must restart your system after you apply this security update.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB902400$\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

Catsrv.dll

2001.12.4414.62

26-Jul-2005

04:30

220,672

SP1QFE

Catsrvut.dll

2001.12.4414.62

26-Jul-2005

04:30

581,632

SP1QFE

Clbcatex.dll

2001.12.4414.62

26-Jul-2005

04:30

110,080

SP1QFE

Clbcatq.dll

2001.12.4414.62

26-Jul-2005

04:30

497,152

SP1QFE

Colbact.dll

2001.12.4414.62

26-Jul-2005

04:30

62,464

SP1QFE

Comadmin.dll

2001.12.4414.62

26-Jul-2005

04:30

187,392

SP1QFE

Comrepl.dll

2001.12.4414.62

26-Jul-2005

04:30

89,600

SP1QFE

Comsvcs.dll

2001.12.4414.62

26-Jul-2005

04:30

1,179,136

SP1QFE

Comuid.dll

2001.12.4414.62

26-Jul-2005

04:31

499,200

SP1QFE

Es.dll

2001.12.4414.62

26-Jul-2005

04:31

227,328

SP1QFE

Migregdb.exe

2001.12.4414.62

22-Jul-2005

23:03

7,680

SP1QFE

Msdtcprx.dll

2001.12.4414.62

26-Jul-2005

04:31

368,640

SP1QFE

Msdtctm.dll

2001.12.4414.62

26-Jul-2005

04:31

973,824

SP1QFE

Msdtcuiu.dll

2001.12.4414.62

26-Jul-2005

04:31

150,528

SP1QFE

Mtxclu.dll

2001.12.4414.62

26-Jul-2005

04:31

64,512

SP1QFE

Mtxoci.dll

2001.12.4414.62

26-Jul-2005

04:31

83,456

SP1QFE

Ole32.dll

5.1.2600.1720

26-Jul-2005

04:31

1,190,400

SP1QFE

Olecli32.dll

5.1.2600.1720

26-Jul-2005

04:31

68,608

SP1QFE

Olecnv32.dll

5.1.2600.1720

26-Jul-2005

04:31

35,328

SP1QFE

Rpcrt4.dll

5.1.2600.1361

06-Mar-2004

02:16

535,552

SP1QFE

Rpcss.dll

5.1.2600.1720

26-Jul-2005

04:31

276,992

SP1QFE

Txflog.dll

2001.12.4414.62

26-Jul-2005

04:31

97,280

SP1QFE

Xolehlp.dll

2001.12.4414.62

26-Jul-2005

04:31

11,776

SP1QFE

Catsrv.dll

2001.12.4414.308

26-Jul-2005

04:39

225,792

SP2GDR

Catsrvut.dll

2001.12.4414.308

26-Jul-2005

04:39

625,152

SP2GDR

Clbcatex.dll

2001.12.4414.308

26-Jul-2005

04:39

110,080

SP2GDR

Clbcatq.dll

2001.12.4414.308

26-Jul-2005

04:39

498,688

SP2GDR

Colbact.dll

2001.12.4414.308

26-Jul-2005

04:39

60,416

SP2GDR

Comadmin.dll

2001.12.4414.308

26-Jul-2005

04:39

195,072

SP2GDR

Comrepl.dll

2001.12.4414.308

26-Jul-2005

04:39

97,792

SP2GDR

Comsvcs.dll

2001.12.4414.308

26-Jul-2005

04:39

1,267,200

SP2GDR

Comuid.dll

2001.12.4414.308

26-Jul-2005

04:39

540,160

SP2GDR

Es.dll

2001.12.4414.308

26-Jul-2005

04:39

243,200

SP2GDR

Migregdb.exe

2001.12.4414.308

25-Jul-2005

23:46

7,680

SP2GDR

Msdtcprx.dll

2001.12.4414.308

26-Jul-2005

04:39

425,472

SP2GDR

Msdtctm.dll

2001.12.4414.308

26-Jul-2005

04:39

945,152

SP2GDR

Msdtcuiu.dll

2001.12.4414.308

26-Jul-2005

04:39

161,280

SP2GDR

Mtxclu.dll

2001.12.4414.308

26-Jul-2005

04:39

66,560

SP2GDR

Mtxoci.dll

2001.12.4414.308

26-Jul-2005

04:39

91,136

SP2GDR

Ole32.dll

5.1.2600.2726

26-Jul-2005

04:39

1,285,120

SP2GDR

Olecli32.dll

5.1.2600.2726

26-Jul-2005

04:39

74,752

SP2GDR

Olecnv32.dll

5.1.2600.2726

26-Jul-2005

04:39

37,888

SP2GDR

Rpcss.dll

5.1.2600.2726

26-Jul-2005

04:39

397,824

SP2GDR

Txflog.dll

2001.12.4414.308

26-Jul-2005

04:39

101,376

SP2GDR

Xolehlp.dll

2001.12.4414.308

26-Jul-2005

04:39

11,776

SP2GDR

Catsrv.dll

2001.12.4414.308

26-Jul-2005

04:20

225,792

SP2QFE

Catsrvut.dll

2001.12.4414.308

26-Jul-2005

04:20

625,152

SP2QFE

Clbcatex.dll

2001.12.4414.308

26-Jul-2005

04:20

110,080

SP2QFE

Clbcatq.dll

2001.12.4414.308

26-Jul-2005

04:20

498,688

SP2QFE

Colbact.dll

2001.12.4414.308

26-Jul-2005

04:20

60,416

SP2QFE

Comadmin.dll

2001.12.4414.308

26-Jul-2005

04:20

195,072

SP2QFE

Comrepl.dll

2001.12.4414.308

26-Jul-2005

04:20

97,792

SP2QFE

Comsvcs.dll

2001.12.4414.308

26-Jul-2005

04:20

1,267,200

SP2QFE

Comuid.dll

2001.12.4414.308

26-Jul-2005

04:20

540,160

SP2QFE

Es.dll

2001.12.4414.308

26-Jul-2005

04:20

243,200

SP2QFE

Migregdb.exe

2001.12.4414.308

25-Jul-2005

23:42

8,704

SP2QFE

Msdtcprx.dll

2001.12.4414.308

26-Jul-2005

04:20

425,472

SP2QFE

Msdtctm.dll

2001.12.4414.308

26-Jul-2005

04:20

945,152

SP2QFE

Msdtcuiu.dll

2001.12.4414.308

26-Jul-2005

04:20

161,280

SP2QFE

Mtxclu.dll

2001.12.4414.308

26-Jul-2005

04:20

66,560

SP2QFE

Mtxoci.dll

2001.12.4414.308

26-Jul-2005

04:20

91,136

SP2QFE

Ole32.dll

5.1.2600.2726

26-Jul-2005

04:20

1,285,632

SP2QFE

Olecli32.dll

5.1.2600.2726

26-Jul-2005

04:20

74,752

SP2QFE

Olecnv32.dll

5.1.2600.2726

26-Jul-2005

04:20

37,376

SP2QFE

Rpcss.dll

5.1.2600.2726

26-Jul-2005

04:20

398,336

SP2QFE

Txflog.dll

2001.12.4414.308

26-Jul-2005

04:20

101,376

SP2QFE

Xolehlp.dll

2001.12.4414.308

26-Jul-2005

04:20

11,776

SP2QFE

Arpidfix.exe

5.1.2600.2726

26-Jul-2005

02:21

30,720

Windows XP Professional x64: File Name Version Date Time Size CPU Folder

Catsrv.dll

2001.12.4720.2492

26-Aug-2005

23:43

418,816

x64

SP1GDR

Catsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:43

1,084,416

x64

SP1GDR

Clbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:43

175,104

x64

SP1GDR

Clbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:43

880,128

x64

SP1GDR

Colbact.dll

2001.12.4720.2492

26-Aug-2005

23:43

97,792

x64

SP1GDR

Comadmin.dll

2001.12.4720.2492

26-Aug-2005

23:43

288,768

x64

SP1GDR

Comrepl.dll

2001.12.4720.2492

26-Aug-2005

23:43

188,928

x64

SP1GDR

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:43

2,156,544

x64

SP1GDR

Comuid.dll

2001.12.4720.2492

26-Aug-2005

23:43

1,478,144

x64

SP1GDR

Es.dll

2001.12.4720.2492

26-Aug-2005

23:43

365,568

x64

SP1GDR

Msdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:43

824,320

x64

SP1GDR

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

23:43

2,052,096

x64

SP1GDR

Msdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:43

291,328

x64

SP1GDR

Mtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:43

144,896

x64

SP1GDR

Mtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:43

30,720

x64

SP1GDR

Mtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:43

175,104

x64

SP1GDR

Ole32.dll

5.2.3790.2492

26-Aug-2005

23:43

2,543,104

x64

SP1GDR

Olecli32.dll

5.2.3790.2492

26-Aug-2005

23:43

131,584

x64

SP1GDR

Olecnv32.dll

5.2.3790.2492

26-Aug-2005

23:43

56,832

x64

SP1GDR

Rpcss.dll

5.2.3790.2492

26-Aug-2005

23:43

691,200

x64

SP1GDR

Stclient.dll

2001.12.4720.2492

26-Aug-2005

23:43

101,888

x64

SP1GDR

Txflog.dll

2001.12.4720.2492

26-Aug-2005

23:43

179,200

x64

SP1GDR

Wcatsrv.dll

2001.12.4720.2492

26-Aug-2005

23:43

274,432

x86

SP1GDR\WOW

Wcatsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:43

619,520

x86

SP1GDR\WOW

Wclbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:43

104,960

x86

SP1GDR\WOW

Wclbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:43

512,000

x86

SP1GDR\WOW

Wcolbact.dll

2001.12.4720.2492

26-Aug-2005

23:43

58,880

x86

SP1GDR\WOW

Wcomadmin.dll

2001.12.4720.2492

26-Aug-2005

23:43

196,608

x86

SP1GDR\WOW

Wcomsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:43

1,247,744

x86

SP1GDR\WOW

Wcomuid.dll

2001.12.4720.2492

26-Aug-2005

23:43

596,480

x86

SP1GDR\WOW

Wes.dll

2001.12.4720.2492

26-Aug-2005

23:43

238,592

x86

SP1GDR\WOW

Wmsdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:43

466,432

x86

SP1GDR\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:43

165,888

x86

SP1GDR\WOW

Wmtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:43

78,848

x86

SP1GDR\WOW

Wmtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:43

20,992

x86

SP1GDR\WOW

Wmtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:43

111,104

x86

SP1GDR\WOW

Wole32.dll

5.2.3790.2492

26-Aug-2005

23:43

1,245,184

x86

SP1GDR\WOW

Wolecli32.dll

5.2.3790.2492

26-Aug-2005

23:43

75,776

SP1GDR\WOW

Wolecnv32.dll

5.2.3790.2492

26-Aug-2005

23:43

38,912

x86

SP1GDR\WOW

Wstclient.dll

2001.12.4720.2492

26-Aug-2005

23:43

64,000

x86

SP1GDR\WOW

Wtxflog.dll

2001.12.4720.2492

26-Aug-2005

23:43

98,816

x86

SP1GDR\WOW

Catsrv.dll

2001.12.4720.2492

26-Aug-2005

23:47

418,304

x64

SP1QFE

Catsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:47

1,084,416

x64

SP1QFE

Clbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:47

175,104

x64

SP1QFE

Clbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:47

882,176

x64

SP1QFE

Colbact.dll

2001.12.4720.2492

26-Aug-2005

23:47

97,280

x64

SP1QFE

Comadmin.dll

2001.12.4720.2492

26-Aug-2005

23:47

288,768

x64

SP1QFE

Comrepl.dll

2001.12.4720.2492

26-Aug-2005

23:47

188,928

x64

SP1QFE

Comsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:47

2,191,872

x64

SP1QFE

Comuid.dll

2001.12.4720.2492

26-Aug-2005

23:47

1,478,144

x64

SP1QFE

Es.dll

2001.12.4720.2492

26-Aug-2005

23:47

365,568

x64

SP1QFE

Msdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:47

825,344

x64

SP1QFE

Msdtctm.dll

2001.12.4720.2517

26-Aug-2005

23:47

2,053,120

x64

SP1QFE

Msdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:47

291,328

x64

SP1QFE

Mtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:47

144,896

x64

SP1QFE

Mtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:47

30,208

x64

SP1QFE

Mtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:47

175,104

x64

SP1QFE

Ole32.dll

5.2.3790.2492

26-Aug-2005

23:47

2,544,640

x64

SP1QFE

Olecli32.dll

5.2.3790.2492

26-Aug-2005

23:47

131,584

x64

SP1QFE

Olecnv32.dll

5.2.3790.2492

26-Aug-2005

23:47

56,832

x64

SP1QFE

Rpcss.dll

5.2.3790.2492

26-Aug-2005

23:47

692,224

x64

SP1QFE

Stclient.dll

2001.12.4720.2492

26-Aug-2005

23:47

101,888

x64

SP1QFE

Txflog.dll

2001.12.4720.2492

26-Aug-2005

23:47

179,200

x64

SP1QFE

Wcatsrv.dll

2001.12.4720.2492

26-Aug-2005

23:47

274,432

x86

SP1QFE\WOW

Wcatsrvut.dll

2001.12.4720.2492

26-Aug-2005

23:47

619,520

x86

SP1QFE\WOW

Wclbcatex.dll

2001.12.4720.2492

26-Aug-2005

23:47

104,960

x86

SP1QFE\WOW

Wclbcatq.dll

2001.12.4720.2492

26-Aug-2005

23:47

514,048

x86

SP1QFE\WOW

Wcolbact.dll

2001.12.4720.2492

26-Aug-2005

23:47

58,880

x86

SP1QFE\WOW

Wcomadmin.dll

2001.12.4720.2492

26-Aug-2005

23:47

196,608

x86

SP1QFE\WOW

Wcomsvcs.dll

2001.12.4720.2517

26-Aug-2005

23:47

1,267,712

x86

SP1QFE\WOW

Wcomuid.dll

2001.12.4720.2492

26-Aug-2005

23:47

596,480

x86

SP1QFE\WOW

Wes.dll

2001.12.4720.2492

26-Aug-2005

23:47

238,592

x86

SP1QFE\WOW

Wmsdtcprx.dll

2001.12.4720.2492

26-Aug-2005

23:47

466,944

x86

SP1QFE\WOW

Wmsdtcuiu.dll

2001.12.4720.2492

26-Aug-2005

23:47

165,888

x86

SP1QFE\WOW

Wmtxclu.dll

2001.12.4720.2492

26-Aug-2005

23:47

78,848

x86

SP1QFE\WOW

Wmtxdm.dll

2001.12.4720.2492

26-Aug-2005

23:47

20,992

x86

SP1QFE\WOW

Wmtxoci.dll

2001.12.4720.2492

26-Aug-2005

23:47

111,104

x86

SP1QFE\WOW

Wole32.dll

5.2.3790.2492

26-Aug-2005

23:47

1,245,696

x86

SP1QFE\WOW

Wolecli32.dll

5.2.3790.2492

26-Aug-2005

23:47

75,776

SP1QFE\WOW

Wolecnv32.dll

5.2.3790.2492

26-Aug-2005

23:47

38,912

x86

SP1QFE\WOW

Wstclient.dll

2001.12.4720.2492

26-Aug-2005

23:47

64,000

x86

SP1QFE\WOW

Wtxflog.dll

2001.12.4720.2492

26-Aug-2005

23:47

98,816

x86

SP1QFE\WOW

Arpidfix.exe

5.2.3790.2517

26-Aug-2005

23:49

43,008

x64

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.

Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.

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\KB902400\Filelist

For Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB902400\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 902400 security update into the Windows installation source files. Top of sectionTop of section

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-kb902400-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 KB902400.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-kb902400-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

You must restart your system after you apply this security update.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB902400$\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

08:18

165,648

Catsrvut.dll

2000.2.3529.0

05-Sep-2005

08:18

595,728

Clbcatex.dll

2000.2.3529.0

05-Sep-2005

08:18

97,040

Clbcatq.dll

2000.2.3529.0

05-Sep-2005

08:18

551,184

Colbact.dll

2000.2.3529.0

05-Sep-2005

08:18

41,744

Comadmin.dll

2000.2.3529.0

05-Sep-2005

08:18

197,904

Comrepl.dll

2000.2.3529.0

05-Sep-2005

08:18

97,552

Comsetup.dll

2000.2.3421.3529

05-Sep-2005

08:18

342,288

Comsvcs.dll

2000.2.3529.0

05-Sep-2005

08:18

1,471,248

Comuid.dll

2000.2.3529.0

05-Sep-2005

08:18

625,936

Dtcsetup.exe

2000.2.3529.0

30-Aug-2005

04:47

1,833,968

Es.dll

2000.2.3529.0

05-Sep-2005

08:18

242,448

Msdtclog.dll

2000.2.3529.0

05-Sep-2005

08:18

96,016

Msdtcprx.dll

2000.2.3529.0

05-Sep-2005

08:18

726,288

Msdtctm.dll

2000.2.3529.0

05-Sep-2005

08:18

1,200,400

Msdtcui.dll

2000.2.3529.0

05-Sep-2005

08:18

153,872

Mtstocom.exe

2000.2.3529.0

30-Aug-2005

05:05

155,408

Mtxclu.dll

2000.2.3529.0

05-Sep-2005

08:18

52,496

Mtxdm.dll

2000.2.3529.0

05-Sep-2005

08:18

26,896

Mtxlegih.dll

2000.2.3529.0

05-Sep-2005

08:18

35,600

Mtxoci.dll

2000.2.3529.0

05-Sep-2005

08:18

122,640

Ole32.dll

5.0.2195.7059

05-Sep-2005

08:18

957,712

Olecli32.dll

5.0.2195.7009

05-Sep-2005

08:18

69,392

Olecnv32.dll

5.0.2195.7059

05-Sep-2005

08:18

36,624

Rpcrt4.dll

5.0.2195.6904

11-Mar-2004

21:29

449,808

Rpcss.dll

5.0.2195.7059

05-Sep-2005

08:18

212,240

Sp3res.dll

5.0.2195.7040

21-Apr-2005

10:07

6,309,376

Stclient.dll

2000.2.3529.0

05-Sep-2005

08:18

71,440

Txfaux.dll

2000.2.3529.0

05-Sep-2005

08:18

398,608

Xolehlp.dll

2000.2.3529.0

05-Sep-2005

08:18

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\KB902400\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 902400 security update into the Windows installation source files. Top of sectionTop of section

Top of sectionTop of section

Acknowledgments

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

eEye Digital Security for reporting the MSDTC Vulnerability (CAN-2005-2119). •

Cesar Cerrudo of Argeniss for reporting the COM+ Vulnerability (CAN-2005-1978). •

iDefense for reporting the TIP Vulnerability (CAN-2005-1979) and the Distributed TIP Vulnerability (CAN-2005-1980).

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations: •

Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." •

Updates for consumer platforms are available at the Microsoft Update Web site.

Support: •

Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. •

International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Security Resources: •

The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. •

Microsoft Software Update Services •

Microsoft Windows Server Update Services •

Microsoft Baseline Security Analyzer (MBSA) •

Windows Update •

Microsoft Update •

Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166. •

Office Update

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy 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 (October 11, 2005): Bulletin published.