Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS07-058 - Important

Vulnerability in RPC Could Allow Denial of Service (933729)

Published: October 09, 2007 | Updated: October 10, 2007

Version: 1.1

General Information

Executive Summary

This update resolves a privately reported vulnerability. A denial of service vulnerability exists in the remote procedure call (RPC) facility due to a failure in communicating with the NTLM security provider when performing authentication of RPC requests. The vulnerability is documented in its own subsection in the Vulnerability Details section of this bulletin.

This is an important security update for all supported editions of Windows 2000, Windows XP, Windows Server 2003, and Windows Vista. For more information, see the subsection, Affected and Non-Affected Software, in this section.

This security update addresses the vulnerability by validating the RPC request. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. None

Affected and Non-Affected Software

The software listed here have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by This Update
Microsoft Windows 2000 Service Pack 4 Information DisclosureLow MS06-031
Windows XP Service Pack 2 Denial of ServiceImportantNone
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Denial of ServiceImportantNone
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Denial of ServiceImportant None
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Denial of ServiceImportantNone
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Denial of ServiceImportantNone
Windows Vista Denial of ServiceImportantNone
Windows Vista x64 Edition Denial of ServiceImportantNone

I am using an older version of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin have been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareRPC Authentication Vulnerability CVE-2007-2228Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Low

Information Disclosure

Low
Windows XP Service Pack 2 Important

Denial of Service

Important
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Important

Denial of Service

Important
Windows Server 2003 Service pack 1 and Windows Server 2003 Service Pack 2 Important

Denial of Service

Important
Windows Server 2003 x64 Edition and Windows 2003 Service pack 2 Important

Denial of Service

Important
Windows Server 2003 for Itanium-based Systems and Windows Server 2003 with SP1 for Itanium-based Systems Important

Denial of Service

Important
Windows Vista Important

Denial of Service

Important
Windows Vista x64 Edition Important

Denial of Service

Important

A denial of service vulnerability exists in the remote procedure call (RPC) facility due to a failure in communicating with the NTLM security provider when performing authentication of RPC requests. An anonymous attacker could exploit the vulnerability by sending a specially crafted RPC authentication request to a computer over the network. An attacker who successfully exploited this vulnerability could cause the computer to stop responding and automatically restart.

Mitigating Factors for RPC Authentication Vulnerability Could Allow Denial of Service - CVE-2007-2228

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.

Workarounds for RPC Authentication Vulnerability Could Allow Denial of Service - CVE-2007-2228

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

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

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

    Impact of Workaround:Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below.

    Applications that use SMB (CIFS)
    Applications that use mailslots or named pipes (RPC over SMB)
    Server (File and Print Sharing)
    Group Policy
    Net Logon
    Distributed File System (DFS)
    Terminal Server Licensing
    Print Spooler
    Computer Browser
    Remote Procedure Call Locator
    Fax Service
    Indexing Service
    Performance Logs and Alerts
    Systems Management Server
    License Logging Service

  • To help protect from network-based attempts to exploit this vulnerability, use a personal firewall, such as Windows Firewall, which is included with Windows XP and with Windows Server 2003.

    By default, the Windows Firewall feature in Windows XP and 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 Windows Firewall feature by using the Network Setup Wizard, follow these steps:

    1. Click Start and then click Control Panel.
    2. Double-click Network Connections and then click Change Windows Firewall settings.
    3. On the General tab, ensure that the On (recommended) value is selected. This will enable the Windows Firewall.
    4. Once the Windows Firewall is enabled, select Don’t allow exceptions to prohibit all incoming traffic.

    Note If you want to enable certain programs and services to communicate through the firewall, de-select Don’t allow exceptions and click the Exceptions tab. On the Exceptions tab, select the programs, protocols, and services that you want to enable.

    Impact of Workaround:Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below.

    Applications that use SMB (CIFS)
    Applications that use mailslots or named pipes (RPC over SMB)
    Server (File and Print Sharing)
    Group Policy
    Net Logon
    Distributed File System (DFS)
    Terminal Server Licensing
    Print Spooler
    Computer Browser
    Remote Procedure Call Locator
    Fax Service
    Indexing Service
    Performance Logs and Alerts
    Systems Management Server
    License Logging Service

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

FAQ for RPC Authentication Vulnerability Could Allow Denial of Service - CVE-2007-2228:

What is Microsoft RPC Authentication?
To complete any remote procedure call, all distributed applications must create a binding between the client and the server. Microsoft RPC provides multiple levels of authentication. Depending on the authentication level, the origin of the traffic (which security principal sent the traffic) can be verified when the connection is established, when the client starts a new remote procedure call, or during each packet exchange between the client and server. For additional information on RPC and RPC Authentication please see the following MSDN Article.

What is the scope of the vulnerability?
This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. 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?
Specially crafted packets using the NTLMSSP authentication type can cause the RPC service to fail in such a way that could cause the system to restart.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could a user’s system to become non-responsive and restart.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted RPC message and sending the message to an affected system over an affected TCP/UDP port. The message could then cause the RPCSS service to stop responding and cause the vulnerable system to fail in such a way that it could cause a denial of service.

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 system. End users can visit Security At Home. IT professionals can visit TechNet Security Center.

What systems are primarily at risk from the vulnerability?
Both workstations and servers are at risk. Systems that allow RPC traffic from untrusted networks could be at more risk.

What does the update do?
The update removes the vulnerability by validating the RPC request.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

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

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA visit Microsoft Baseline Security Analyzer Web site. The following table provides the MBSA detection summary for this security update.

SoftwareMBSA 1.2.1MBSA 2.0.1
Microsoft Windows 2000 Service Pack 4YesYes
Windows XP Service Pack 2YesYes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2NoYes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2YesYes
Windows Server 2003 x64 EditionNoYes
Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Windows VistaNoSee Note for Windows Vista below
Windows Vista x64 EditionNoSee Note for Windows Vista below

Note for Windows Vista : Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can 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 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

ProductSMS 2.0SMS 2003
Microsoft Windows 2000 Service Pack 4YesYes
Microsoft Windows XP Service Pack 2YesYes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2NoYes
Microsoft Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2YesYes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Microsoft Windows Server 2003 x64 Edition NoYes
Microsoft Windows VistaNo See Note for Windows Vista Below
Microsoft Windows Vista x64 EditionNo See Note for Windows Vista Below

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Affected Software

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

Windows 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue may be included in a future update rollup
Deployment
Installing without user interventionWindows 2000 Service Pack 4:
Windows2000-kb933729-x86-enu /quiet
Installing without restartingWindows 2000 Service Pack 4:
Windows2000-kb933729-x86-enu /norestart
Update log fileWindows 2000 Service Pack 4:
KB933729.og
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingNot applicable
Removal Information Windows 2000 Service Pack 4:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB933729$\Spuninst folder
File Information See the subsection, File Information.
Registry Key Verification For Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB933729\Filelist

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.

For all supported editions of Windows 2000:

File NameVersionDateTimeSize
rpcrt4.dll5.0.2195.709017-Jul-200719:12439,056

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more informationFile Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionWindows XP Service Pack 2:
Windowsxp-kb933729-x86-enu /quiet
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:

Windowsserver-2003-kb933729-x86-enu /quiet

Installing without restartingWindows XP Service Pack 2:
Windowsxp-kb933729-x86-enu /norestart
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:

Windowsserver-2003-kb933729-x86-enu /norestart

Update log fileWindows XP Service Pack 2:
KB933729.log
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB933729$\Spuninst folder
File Information See the subsection, File Information.
Registry Key Verification For all supported 32-bit versions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB933729\Filelist
For all supported x64 editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB933729\Filelist

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.

For all supported 32-bit editions of Windows XP:

File NameVersionDateTimeSizeFolder
rpcrt4.dll5.1.2600.317309-Jul-200713:09584,192SP2GDR
xpsp3res.dll5.1.2600.315513-Jun-200706:53115,712SP2GDR
rpcrt4.dll5.1.2600.317309-Jul-200713:16582,656SP2QFE
xpsp3res.dll5.1.2600.315819-Jun-200707:24350,720SP2QFE

For all supported editions of Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
rpcrt4.dll5.2.3790.297111-Jul-200718:281,717,248X64SP1GDR
wrpcrt4.dll5.2.3790.297111-Jul-200718:28626,176X86SP1GDR\wow
rpcrt4.dll5.2.3790.297111-Jul-200718:281,716,224X64SP1QFE
wrpcrt4.dll5.2.3790.297111-Jul-200718:28626,688X86SP1QFE\wow
rpcrt4.dll5.2.3790.411511-Jul-200718:321,653,248X64SP2GDR
wrpcrt4.dll5.2.3790.411511-Jul-200718:32629,248X86SP2GDR\wow
rpcrt4.dll5.2.3790.411511-Jul-200718:291,653,248X64SP2QFE
wrpcrt4.dll5.2.3790.411511-Jul-200718:29629,248X86SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

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

This security update supports the following setup switches.This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information

  • File Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb933729-x86-enu /quiet
Installing without restartingWindows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
Windowsserver2003-kb933729-x86-enu /norestart
Update log fileKB933729.log
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingThis security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB933729$\Spuninst folder
File Information See the heading, File Information.
Registry Key Verification For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB933729\Filelist

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.

For all supported 32-bit editions of Windows Server 2003:

File NameVersionDateTimeSizeFolder
rpcrt4.dll5.2.3790.297111-Jul-200710:43642,560SP1GDR
rpcrt4.dll5.2.3790.297111-Jul-200709:59643,584SP1QFE
rpcrt4.dll5.2.3790.411511-Jul-200710:38642,048SP2GDR
rpcrt4.dll5.2.3790.411511-Jul-200710:36642,048SP2QFE

For all supported Itanium-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
rpcrt4.dll5.2.3790.297111-Jul-200711:272,462,208IA-64SP1GDR
wrpcrt4.dll5.2.3790.297111-Jul-200711:27626,176X86SP1GDR\wow
rpcrt4.dll5.2.3790.297111-Jul-200711:282,464,256IA-64SP1QFE
wrpcrt4.dll5.2.3790.297111-Jul-200711:28626,688X86SP1QFE\wow
rpcrt4.dll5.2.3790.411511-Jul-200711:312,470,912IA-64SP2GDR
wrpcrt4.dll5.2.3790.411511-Jul-200711:31629,248X86SP2GDR\wow
rpcrt4.dll5.2.3790.411511-Jul-200711:282,470,912IA-64SP2QFE
wrpcrt4.dll5.2.3790.411511-Jul-200711:28629,248X86SP2QFE\wow

For all supported x64-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
rpcrt4.dll5.2.3790.297111-Jul-200718:281,717,248X64SP1GDR
wrpcrt4.dll5.2.3790.297111-Jul-200718:28626,176X86SP1GDR\wow
rpcrt4.dll5.2.3790.297111-Jul-200718:281,716,224X64SP1QFE
wrpcrt4.dll5.2.3790.297111-Jul-200718:28626,688X86SP1QFE\wow
rpcrt4.dll5.2.3790.411511-Jul-200718:321,653,248X64SP2GDR
wrpcrt4.dll5.2.3790.411511-Jul-200718:32629,248X86SP2GDR\wow
rpcrt4.dll5.2.3790.411511-Jul-200718:291,653,248X64SP2QFE
wrpcrt4.dll5.2.3790.411511-Jul-200718:29629,248X86SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionWindows Vista:
Windows6.0-kb933729-x86-enu /quiet
Installing without restartingWindows Vista:
Windows6.0-kb933729-x86-enu /norestart
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingThis security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information Windows Vista:
Use Add or Remove Programs tool in Control Panel or the wusa.exe utility.
File Information See the heading, File Information.

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.

For all supported 32-bit editions of Windows Vista:

File NameVersionDateTimeSizeFolder
rpcrt4.dll6.0.6000.1652517-Jul-200703:18788,992x86_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.16525_none_b203c02547f977dc
rpcrt4.dll6.0.6000.2064117-Jul-200703:27788,992x86_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.20641_none_b273bbf0612aea2c

For all supported x64-based editions of Windows Vista:

File NameVersionDateTimeSizeFolder
rpcrt4.dll6.0.6000.1652517-Jul-200704:251,260,544amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.16525_none_0e225ba90056e912
rpcrt4.dll6.0.6000.2064117-Jul-200704:151,260,544amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.20641_none_0e92577419885b62
rpcrt4.dll6.0.6000.1652517-Jul-200703:15672,256wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.16525_none_187705fb34b7ab0d
rpcrt4.dll6.0.6000.2064117-Jul-200703:28672,256wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6000.20641_none_18e701c64de91d5d

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information

  • File Version Verification

    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.

Other Information

Acknowledgments

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

  • Zero Day Initiative for reporting the Windows RPC Authentication Vulnerability (CVE-2007-2228).

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.

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 9, 2007): Bulletin published.
  • V1.1 (October 10, 2007): Updating bulletin to show XP professional x64 Edition Service Pack 2 as affected software.

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

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.