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

Microsoft Security Bulletin MS09-044 - Critical

Vulnerabilities in Remote Desktop Connection Could Allow Remote Code Execution (970927)

Published: August 11, 2009 | Updated: November 04, 2009

Version: 2.1

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Microsoft Remote Desktop Connection. The vulnerabilities could allow remote code execution if an attacker successfully convinced a user of Terminal Services to connect to a malicious RDP server or if a user visits a specially crafted Web site that exploits this vulnerability. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Important for default versions of RDP on supported editions of Windows Vista, Windows Vista for x64-based Systems, and Remote Desktop Connection Client for Mac 2.0 and is rated Critical for default versions of RDP on all other supported Windows editions. This security update is rated Important for RDP Version 6.0 that administrators can manually install on Windows Server 2003 Service Pack 2 and Windows Server 2003 x64 Edition Service Pack 2 and is rated Critical for all other versions of RDP that administrators can manually install on supported Windows editions. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by changing the way the Remote Desktop Connection deals with unexpected parameters sent by the RDP server and by correctly validating parameters passed to the Remote Desktop Connection ActiveX control methods. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. Microsoft Knowledge Base Article 970927 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

The following software 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

Operating SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 RDP Version 5.0 (KB958471)** and RDP Version 5.0 (KB958470)

RDP Version 5.1 (KB958470)***
RDP Version 5.2 (KB958470)***
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 RDP Version 5.1 (KB958470)
RDP Version 5.2 (KB958469)***
RDP Version 6.1 (KB956744)***
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 RDP Version 6.0 (KB956744)***Remote Code ExecutionImportantNone
Windows XP Service Pack 3 RDP Version 5.2 (KB958469)
RDP Version 6.1 (KB956744)***
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 RDP Version 5.2 (KB958469)Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 RDP Version 6.0 (KB956744)***Remote Code ExecutionImportantNone
Windows Server 2003 Service Pack 2 RDP Version 5.2 (KB958469)Remote Code ExecutionCriticalNone
Windows Server 2003 Service Pack 2 RDP Version 6.0 (KB956744)***Remote Code ExecutionImportantNone
Windows Server 2003 x64 Edition Service Pack 2 RDP Version 5.2 (KB958469)Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2 RDP Version 6.0 (KB956744)***Remote Code ExecutionImportantNone
Windows Server 2003 with SP2 for Itanium-based Systems RDP Version 5.2 (KB958469)Remote Code ExecutionCriticalNone
Windows Vista RDP Version 6.0 (KB956744)Remote Code ExecutionImportantNone
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 RDP Version 6.1 (KB956744)Remote Code ExecutionCriticalNone
Windows Vista x64 Edition RDP Version 6.0 (KB956744)Remote Code ExecutionImportantNone
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 RDP Version 6.1 (KB956744)Remote Code ExecutionCriticalNone
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* RDP Version 6.1 (KB956744)Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* RDP Version 6.1 (KB956744)Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 RDP Version 6.1 (KB956744)Remote Code ExecutionCriticalNone

*Windows Server 2008 server core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

**Users of RDP Version 5.0 on Microsoft Windows 2000 Service Pack 4 must install both KB958471 and KB958470.

***Administrators may have manually installed this out-of-box download.

Affected Software

SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Remote Desktop Connection Client for Mac 2.0**** (KB974283)Remote Code ExecutionImportantNone

****This download upgrades Remote Desktop Connection Client for Mac 2.0 to Remote Desktop Connection Client for Mac 2.0.1, which addresses the vulnerability.

Non-Affected Software

Operating System
Windows 7 for 32-bit Systems
Windows 7 for x64-based Systems
Windows Server 2008 R2 for x64-based Systems
Windows Server 2008 R2 for Itanium-based Systems

Why was this bulletin revised on November 4, 2009? 
This bulletin was revised to add known issues to this update due to limited RDP drawing failures identified with the update for RDP Version 5.2 contained in KB958469. Microsoft Knowledge Base Article 970927 contains workarounds and a fix for this issue.

Why was this bulletin revised on August 13, 2009? 
This bulletin was revised to effect several corrections:

  • Corrected the update package KBs for RDP Version 5.2 on Windows XP Service Pack 2 and on Windows XP Service Pack 3.
  • Corrected the RDP version and severity for Windows XP Professional x64 Edition Service Pack 2.
  • Corrected the update package KB for Remote Desktop Connection Client for Mac 2.0.
  • Clarified mitigating factors for CVE-2009-1133 by adding the Web-based attack scenario mitigating factor.
  • Clarified workarounds for CVE-2009-1133:
    • Added Windows Server 2003 to the workaround, Restrict Access to mstscax.dll.
    • Added the workaround, Prevent the Remote Desktop Connection ActiveX control from running in Internet Explorer.

Where are the file information details? 
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

What are the known issues that customers may experience when installing this security update? 
Microsoft Knowledge Base Article 970927 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

What are the default installations of Remote Desktop Connection? 
Many versions of Microsoft Windows are delivered with a default version of the Remote Desktop Connection (RDP) client. These versions are referred to as "in-box" components. However, a user or administrator may install more recent versions of the Remote Desktop Connection client. These more recent versions that you can install are referred to as "out of box" installations.

How can I determine the version of the RDP client installed on my system? 
To determine your version of the RDP client, launch the RDP Client from the Start menu, click the top-left icon in the title bar, and select About.

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

I am using an older release 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 releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

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

Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the August bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Operating SystemComponentRemote Desktop Connection Heap Overflow Vulnerability - CVE-2009-1133 Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability - CVE-2009-1929Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 RDP Version 5.0
RDP Version 5.1
RDP Version 5.2
Critical 
Remote Code Execution
Not applicable Critical
Windows XP Service Pack 2RDP Version 5.1
RDP Version 5.2
Critical 
Remote Code Execution
Not applicable Critical
Windows XP Service Pack 2RDP Version 6.0 Important 
Remote Code Execution
Not applicable Important
Windows XP Service Pack 2RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Service Pack 3RDP Version 5.2 Critical 
Remote Code Execution
Not applicable Critical
Windows XP Service Pack 3RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Professional x64 Edition Service Pack 2RDP Version 5.2 Critical 
Remote Code Execution
Not applicable Critical
Windows XP Professional x64 Edition Service Pack 2RDP Version 6.0 Important 
Remote Code Execution
Not applicable Important
Windows Server 2003 Service Pack 2RDP Version 5.2 Critical 
Remote Code Execution
Not applicable Critical
Windows Server 2003 Service Pack 2RDP Version 6.0 Important
Remote Code Execution
Not applicable Important
Windows Server 2003 x64 Edition Service Pack 2RDP Version 5.2 Critical 
Remote Code Execution
Not applicable Critical
Windows Server 2003 x64 Edition Service Pack 2RDP Version 6.0 Important
Remote Code Execution
Not applicable Important
Windows Server 2003 with SP2 for Itanium-based SystemsRDP Version 5.2 Critical 
Remote Code Execution
Not applicable Critical
Windows VistaRDP Version 6.0 Important 
Remote Code Execution
Not applicable Important
Windows Vista Service Pack 1 and Windows Vista Service Pack 2RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Vista x64 EditionRDP Version 6.0 Important 
Remote Code Execution
Not applicable Important
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2RDP Version 6.1 Important 
Remote Code Execution
Critical 
Remote Code Execution
Critical

*Windows Server 2008 server core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
SoftwareRemote Desktop Connection Heap Overflow Vulnerability – CVE-2009-1133Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability – CVE-2009-1929Aggregate Severity Rating
Remote Desktop Connection Client for Mac 2.0**** Important 
Remote Code Execution
Not applicable Important

****This software upgrades Remote Desktop Connection Client for Mac 2.0 to Remote Desktop Connection Client for Mac 2.0.1, which addresses the vulnerability.

A remote code execution vulnerability exists in the way that Microsoft Remote Desktop Connection (formerly known as Terminal Services Client) processes specific parameters returned by the RDP server. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1133.

Mitigating Factors for Remote Desktop Connection Heap Overflow Vulnerability - CVE-2009-1133

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:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • RDP servers are not affected by this vulnerability. Only RDP clients are affected.
  • In RDP Version 6.0 and RDP Version 6.1, the vulnerability cannot be exploited by a malicious Web site that invokes the RDP ActiveX control, which connects the session to a malicious RDP server.

Workarounds for Remote Desktop Connection Heap Overflow Vulnerability - CVE-2009-1133

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:

  • Restrict access to mstscax.dll

    Note You must be an administrator to use these commands.

    Windows XP and Windows Server 2003

    Run the following commands from a command prompt:

    cacls %windir%\system32\mstscax.dll /E /P everyone:N
    cacls %windir%\sysWOW64\mstscax.dll /E /P everyone:N

    Windows Vista and Windows Server 2008

    Run the following commands from an elevated command prompt:

    takeown /F %windir%\system32\mstscax.dll
    cacls %windir%\system32\mstscax.dll /E /P everyone:N
    takeown /F %windir%\SysWOW64\mstscax.dll
    cacls %windir%\SysWOW64\mstscax.dll /E /P everyone:N
    for /F "tokens=*" %G IN ('dir /b /s %windir%\winsxs\mstscax.dll') DO takeown /F %G && cacls %G /E /P everyone:N

    Impact of workaround.After performing these steps, you will not be able to make outbound Remote Desktop connections.

    How to undo the workaround

    Note You must be an administrator to use these commands.

    Windows XP and Windows Server 2003

    Run the following commands from a command prompt:

    cacls %windir%\system32\mstscax.dll /E /R everyone
    cacls %windir%\SysWOW64\mstscax.dll /E /R everyone

    Windows Vista and Windows Server 2008

    Run the following commands from an elevated command prompt:

    cacls %windir%\system32\mstscax.dll /E /R everyone
    cacls %windir%\SysWOW64\mstscax.dll /E /R everyone
    for /F "tokens=*" %G IN ('dir /b /s %windir%\winsxs\mstscax.dll') DO cacls %G /E /R everyone

  • Prevent the Remote Desktop Connection ActiveX control from running in Internet Explorer

    You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

    Note This workaround prevents exploitation through the Web-based attack vector, but it does not protect the user against manually initiating a connection to a malicious RDP server.

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

    Follow these steps to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

    1. Create a text file named Disable_Remote_Desktop_ActiveX.reg with the following contents:

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}]
      "Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}]"Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4EB89FF4-7F78-4A0F-8B8D-2BF02E94E4B2}] "Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{4EB89FF4-7F78-4A0F-8B8D-2BF02E94E4B2}]"Compatibility Flags"=dword:00000400
    2. Apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.

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

    Group Policy collection

    What is Group Policy Object Editor?

    Core Group Policy Tools and Settings

    Note You must restart Internet Explorer for your changes to take effect.

    Impact of workaround. Users will not be able to start remote desktop connections from within Web pages.

    How to undo the workaround. Delete the registry keys previously added in implementing this workaround.

FAQ for Remote Desktop Connection Heap Overflow Vulnerability - CVE-2009-1133

What is the scope of the vulnerability? 
This vulnerability could allow remote code execution. If a user is logged on with administrative privileges, 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 privileges. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.

What causes the vulnerability? 
A remote code execution vulnerability exists in the way that the Microsoft Remote Desktop Connection processes specific parameters returned by the RDP server. This issue results in a heap overflow on the client that can be leveraged by the attacker to execute arbitrary code with the privileges of the logged-on user.

What is the Microsoft Remote Desktop Protocol? 
The Microsoft Remote Desktop Protocol (RDP) provides remote display and input capabilities over network connections for Microsoft Windows-based applications running on a server. RDP is based on, and is an extension of, the ITU T.120 family of protocols. RDP is a multiple-channel capable protocol that allows for separate virtual channels for carrying device communication and presentation data from the server, as well as encryption of the session. RDP provides an extensible base and supports up to 64,000 separate channels for data transmission and provisions for multipoint transmission. On some platforms, Microsoft Remote Desktop Connection is called Terminal Services Client.

Microsoft Windows implements RDP as follows:

  • Windows 2000: Terminal Services includes enhanced RDP Version 5.0.
  • Windows XP Service Pack 2: Uses RDP Version 5.1 for Remote Desktop Connection and for Remote Assistant. Windows XP also includes Remote Desktop Web Connection, which is an updated version of the Terminal Services Advanced Client (TSAC), an RDP client based on a Microsoft ActiveX control. Remote Desktop Web Connection supports RDP Version 5.1 and is backward compatible with RDP Version 5.0. In addition, two out-of-box updates are available which implement RDP Version 6.0 and RDP Version 6.1 on Windows XP Service Pack 2 respectively.
  • Windows XP Service Pack 3: Uses RDP Version 5.2 for Remote Desktop Connection and for Remote Assistance.
  • Windows Server 2003 Service Pack 2: Uses RDP Version 5.2 for Remote Desktop Connection and for Remote Assistant. Remote Desktop Web Connection supports RDP Version 5.2 and is backward compatible with RDP Versions 5.1 and 5.0. In addition, an out-of-box update is available which implements RDP Version 6.0 on these platforms.
  • Windows Vista : Uses RDP Version 6.0 for Remote Desktop Connection.
  • Windows Server 2008, Windows Vista Service Pack 1, and Windows Vista Service Pack 2: Uses RDP Version 6.1 for Remote Desktop Connection.

Why is this vulnerability rated Critical for all versions of RDP with the exception of RDP Version 6.0 and RDP Version 6.1? 
This vulnerability is rated Critical for RDP Version 5.0, RDP Version 5.1, and RDP Version 5.2 because of a specific attack scenario applicable to these RDP versions. In this attack scenario, an attacker could host a specially crafted Web site that is designed to exploit this vulnerability. Such a Web site could invoke the RDP ActiveX control without further user interaction after visiting the Web site and cause the control to connect the session to a malicious RDP server. On RDP Version 6.0 and RDP Version 6.1, exploitation requires the user to accept the connection by interacting with the user interface.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site and then convince a user to view the Web site. The Web site would then invoke the RDP Client ActiveX control to connect the session to a malicious RDP server. An attacker could also convince a user to manually connect to a remote RDP server in order to exploit the vulnerability.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user be logged on and visiting a Web site or engaged in a remote connection with another system for any malicious action to occur. Therefore, workstations or clients intended to connect to terminal servers are particularly affected by this vulnerability.

What does the update do? 
This security update addresses the vulnerability by changing the way that the Remote Desktop Connection deals with unexpected parameters sent by the RDP server.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No, 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.

A remote code execution vulnerability exists in the Microsoft Terminal Services Client ActiveX control. An attacker could exploit the vulnerability by constructing a specially crafted Web page that could allow remote code execution if a user visited that page. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1929.

Mitigating Factors for Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability - CVE-2009-1929

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:

  • By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.
  • By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • RDP Version 5.0, RDP Version 5.1, RDP Version 5.2, RDP Version 6.0, and Remote Desktop Connection Client for Mac 2.0 are not affected by this vulnerability.
  • RDP servers are not affected by this vulnerability. Only RDP clients are affected.

Workarounds for Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability - CVE-2009-1929

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:

  • Prevent the Remote Desktop Connection ActiveX control from running in Internet Explorer

    You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

    Note This workaround prevents exploitation through the Web-based attack vector, but it does not protect the user against manually initiating a connection to a malicious RDP server.

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

    Follow these steps to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

    1. Create a text file named Disable_Remote_Desktop_ActiveX.reg with the following contents:

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}]
      "Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}]"Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4EB89FF4-7F78-4A0F-8B8D-2BF02E94E4B2}] "Compatibility Flags"=dword:00000400

      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{4EB89FF4-7F78-4A0F-8B8D-2BF02E94E4B2}]"Compatibility Flags"=dword:00000400
    2. Apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.

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

    Group Policy collection

    What is Group Policy Object Editor?

    Core Group Policy Tools and Settings

    Note You must restart Internet Explorer for your changes to take effect.

    Impact of workaround. Users will not be able to start remote desktop connections from within Web pages.

    How to undo the workaround. Delete the registry keys previously added in implementing this workaround.

  • Set Internet and Local intranet security zone settings to "High" to prompt before running ActiveX Controls and Active Scripting in these zones

    You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls and Active Scripting. You can do this by setting your browser security to High.

    To raise the browsing security level in Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of workaround. There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.

FAQ for Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability - CVE-2009-1929

What is the scope of the vulnerability? 
This vulnerability could allow remote code execution. If a user is logged on with administrative privileges, 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 privileges. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.

What causes the vulnerability? 
The Remote Desktop Web Connection ActiveX control methods do not perform sufficient parameter validation.

What is the Remote Desktop Web Connection ActiveX control? 
The Remote Desktop Web Connection ActiveX control allows you to access your computer, via the Internet, from another computer using Internet Explorer.

What is the Microsoft Remote Desktop Protocol? 
The Microsoft Remote Desktop Protocol (RDP) provides remote display and input capabilities over network connections for Microsoft Windows-based applications running on a server. RDP is based on, and an extension of, the ITU T.120 family of protocols. RDP is a multiple-channel capable protocol that allows for separate virtual channels for carrying device communication and presentation data from the server, as well as encryption of the session. RDP provides an extensible base and supports up to 64,000 separate channels for data transmission and provisions for multipoint transmission. On some platforms, Microsoft Remote Desktop Connection is called Terminal Services Client.

Microsoft Windows implements RDP as follows:

  • Windows 2000: Terminal Services includes enhanced RDP Version 5.0.
  • Windows XP Service Pack 2: Uses RDP Version 5.1 for Remote Desktop Connection and for Remote Assistant. Windows XP also includes Remote Desktop Web Connection, which is an updated version of the Terminal Services Advanced Client (TSAC), an RDP client based on a Microsoft ActiveX control. Remote Desktop Web Connection supports RDP Version 5.1 and is backward compatible with RDP Version 5.0. In addition, two out-of-box updates are available which implement RDP Version 6.0 and RDP Version 6.1 on Windows XP Service Pack 2 respectively.
  • Windows XP Service Pack 3: Uses RDP Version 5.2 for Remote Desktop Connection and for Remote Assistance.
  • Windows Server 2003 Service Pack 2: Uses RDP Version 5.2 for Remote Desktop Connection and for Remote Assistant. Remote Desktop Web Connection supports RDP Version 5.2 and is backward compatible with RDP Versions 5.1 and 5.0. In addition, an out-of-box update is available which implements RDP Version 6.0 on these platforms.
  • Windows Vista : Uses RDP Version 6.0 for Remote Desktop Connection.
  • Windows Server 2008, Windows Vista Service Pack 1, and Windows Vista Service Pack 2: Uses RDP Version 6.1 for Remote Desktop Connection.

What is the Internet Explorer Enhanced Security Configuration?

Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.
  • Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
  • Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
  • Multimedia content is disabled. This setting prevents music, animations, and video clips from running.

For more information regarding Internet Explorer Enhanced Security Configuration, see the guide, Managing Internet Explorer Enhanced Security Configuration.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code on a users system. This could allow an attacker to take complete control of the affected system.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site. The Web site would invoke the vulnerable ActiveX control and subsequently exploit the vulnerability.

Malicious Web sites can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user be logged on and visiting a Web site or engaged in a remote connection with another system for any malicious action to occur. Therefore, workstations or clients intended to connect to terminal servers are particularly affected by this vulnerability.

Clients that are being used to connect to Web-based Terminal Services (RDP) servers are particularly affected by this vulnerability, as they will have the control installed and operational. Other clients may be affected if they have the control installed, or may become affected if the users accepts installation of the control by a malicious web server.

What does the update do? 
The update addresses the vulnerability by correctly validating parameters for the Remote Desktop Web Connection ActiveX control methods.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No, 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.

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 and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

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.

Note Starting August 1, 2009, Microsoft will discontinue support for Office Update and the Office Update Inventory Tool. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

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.

The following table provides the MBSA detection summary for this security update.

Software MBSA 2.1
Microsoft Windows 2000 Service Pack 4Yes
Windows XP Service Pack 2 and Windows XP Service Pack 3Yes
Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2003 with SP2 for Itanium-based SystemsYes
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2Yes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2Yes

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

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

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Windows 2000 Service Pack 4NoNoYesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3NoNoYesYes
Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 2NoNoYesYes
Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes

For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

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, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 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.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

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 interventionRDP Version 5.0 on Windows 2000 Service Pack 4*: Windows2000-kb958470-x86-enu /quiet
RDP Version 5.0 on Windows 2000 Service Pack 4*: Windows2000-kb958471-x86-enu /quiet
RDP Version 5.1 on Windows 2000 Service Pack 4**: Windows2000-kb958470-x86-enu /quiet
RDP Version 5.2 on Windows 2000 Service Pack 4**: Windows2000-kb958470-x86-enu /quiet
Installing without restartingRDP Version 5.0 on Windows 2000 Service Pack 4*: Windows2000-kb958470-x86-enu /norestart
RDP Version 5.0 on Windows 2000 Service Pack 4*: Windows2000-kb958471-x86-enu /norestart
RDP Version 5.1 on Windows 2000 Service Pack 4**: Windows2000-kb958470-x86-enu /norestart
RDP Version 5.2 on Windows 2000 Service Pack 4**: Windows2000-kb958470-x86-enu /norestart
Update log fileKb958471.log*
kb958470.log*
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, 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%\$NTUninstallKB958471$\Spuninst folder
%Windir%\$NTUninstallKB958470$\Spuninst folder
File Information See Microsoft Knowledge Base Article 970927
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB958471\Filelist
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB958470\Filelist

*Customers of Microsoft Windows 2000 Service Pack 4 must install KB958471 prior to installing KB958470.

**Administrators may have manually installed this out-of-box download.

Deployment Information

Installing the Update

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

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

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 Displays 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 editions of Microsoft Windows, the following steps may be different on your system. 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 edition of the operating system, or the programs that are installed on your system, 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 system 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 interventionRDP Version 5.1 on Windows XP Service Pack 2: Windowsxp-kb958470-x86-enu /quiet
RDP Version 5.2 on Windows XP Service Pack 2*: Windowsxp-kb958469-x86-enu /quiet
RDP Version 6.0 on Windows XP Service Pack 2*: Windowsxp-kb956744-x86-enu /quiet
RDP Version 6.1 on Windows XP Service Pack 2*: Windowsxp-kb956744-x86-enu /quiet
RDP Version 5.2 on Windows XP Service Pack 3: windowsxp-kb958469-x86-enu /quiet
RDP Version 6.1 on Windows XP Service Pack 3*: windowsxp-kb956744-x86-enu /quiet
RDP Version 5.2 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb958469-x64-enu /quiet
RDP Version 6.0 on Windows XP Professional x64 Edition Service Pack 2*:
WindowsServer2003.WindowsXP-kb956744-x64-enu /quiet
Installing without restartingRDP Version 5.1 on Windows XP Service Pack 2: Windowsxp-kb958470-x86-enu /norestart
RDP Version 5.2 on Windows XP Service Pack 2*: Windowsxp-kb958469-x86-enu /norestart
RDP Version 6.0 on Windows XP Service Pack 2*: Windowsxp-kb956744-x86-enu /norestart
RDP Version 6.1 on Windows XP Service Pack 2*: Windowsxp-kb956744-x86-enu /norestart
RDP Version 5.2 on Windows XP Service Pack 3: windowsxp-kb958469-x86-enu /norestart
RDP Version 6.1 on Windows XP Service Pack 3*: windowsxp-kb956744-x86-enu /norestart
RDP Version 5.2 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb958469-x64-enu /norestart
RDP Version 6.0 on Windows XP Professional x64 Edition Service Pack 2*:
WindowsServer2003.WindowsXP-kb956744-x64-enu /norestart
Update log fileFor RDP Version 5.1: KB958470.log
For RDP Version 5.2: KB958469.log
For RDP Version 6.0 and RDP Version 6.1: KB956744.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingNot applicable
Removal Information For RDP Version 5.1, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB958470$\Spuninst folder
For RDP Version 5.2, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB958469$\Spuninst folder
For RDP Version 6.0 and RDP Version 6.1, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB956744$\Spuninst folder
File Information See Microsoft Knowledge Base Article 970927
Registry Key Verification For RDP Version 5.1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB958470\Filelist
For RDP Version 5.2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB958469\Filelist
For RDP Version 6.0 and RDP Version 6.1 on Windows XP Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB956744\Filelist
For RDP Version 6.0 on Windows XP Professional x64 Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB956744\Filelist

*Administrators may have manually installed this out-of-box download.

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

Deployment Information

Installing the Update

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

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

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 Displays 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 editions of Microsoft Windows, the following steps may be different on your system. 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 edition of the operating system, or the programs that are installed on your system, 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 system 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 interventionRDP Version 5.2 on Windows Server 2003 Service Pack 2:
Windowsserver2003-kb958469-x86-enu /quiet
RDP Version 6.0 on Windows Server 2003 Service Pack 2*:
Windowsserver2003-kb956744-x86-enu /quiet
RDP Version 5.2 on Windows Server 2003 x64 Edition Service Pack 2:
Windowsserver2003.WindowsXP-KB958469-x64-enu /quiet
RDP Version 6.0 on Windows Server 2003 x64 Edition Service Pack 2*:
Windowsserver2003.WindowsXP-KB956744-x64-enu /quiet
RDP Version 5.2 on Windows Server 2003 with SP2 for Itanium-based Systems:
Windowsserver2003-KB958469-ia64-enu /quiet
Installing without restartingRDP Version 5.2 on Windows Server 2003 Service Pack 2:
Windowsserver2003-kb958469-x86-enu /norestart
RDP Version 6.0 on Windows Server 2003 Service Pack 2*:
Windowsserver2003-kb956744-x86-enu /norestart
RDP Version 5.2 on Windows Server 2003 x64 Edition Service Pack 2:
Windowsserver2003.WindowsXP-KB958469-x64-enu /norestart
RDP Version 6.0 on Windows Server 2003 x64 Edition Service Pack 2*:
Windowsserver2003.WindowsXP-KB956744-x64-enu /norestart
RDP Version 5.2 on Windows Server 2003 with SP2 for Itanium-based Systems:
Windowsserver2003-KB958469-ia64-enu /norestart
Update log fileKB956744.log or
KB958469.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB956744$\Spuninst folder or
%Windir%\$NTUninstallKB958469$\Spuninst folder
File Information See Microsoft Knowledge Base Article 970927
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB956744\Filelist or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB958469\Filelist

*Administrators may have manually installed this out-of-box download.

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.

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

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

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 Displays 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 editions of Microsoft Windows, the following steps may be different on your system. 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 edition of the operating system, or the programs that are installed on your system, 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 system 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 interventionRDP Version 6.0 on Windows Vista:
Windows6.0-KB956744-x86 /quiet
RDP Version 6.1 on Windows Vista Service Pack 1: Windows6.0-KB956744-x86 /quiet
RDP Version 6.1 on Windows Vista Service Pack 2: Windows6.0-KB956744-x86 /quiet
RDP Version 6.0 on Windows Vista x64 Edition:
Windows6.0-KB956744-x64 /quiet
RDP Version 6.1 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB956744-x64 /quiet
RDP Version 6.1 on Windows Vista x64 Edition Service Pack 2:
Windows6.0-KB956744-x64 /quiet
Installing without restartingRDP Version 6.0 on Windows Vista:
Windows6.0-KB956744-x86 /norestart
RDP Version 6.1 on Windows Vista Service Pack 1: Windows6.0-KB956744-x86 /norestart
RDP Version 6.1 on Windows Vista Service Pack 2: Windows6.0-KB956744-x86 /norestart
RDP Version 6.0 on Windows Vista x64 Edition:
Windows6.0-KB956744-x64 /norestart
RDP Version 6.1 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB956744-x64 /norestart
RDP Version 6.1 on Windows Vista x64 Edition Service Pack 2:
Windows6.0-KB956744-x64 /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingNot applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 970927
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether 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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (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 interventionRDP Version 6.1 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB956744-x86 /quiet
RDP Version 6.1 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB956744-x64 /quiet
RDP Version 6.1 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB956744-ia64 /quiet
Installing without restartingRDP Version 6.1 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB956744-x86 /norestart
RDP Version 6.1 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB956744-x64 /norestart
RDP Version 6.1 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB956744-ia64 /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingNot applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 970927
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether 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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Microsoft Remote Desktop Connection Client for Mac 2.0

Deployment Information

Prerequisites

Supported Operating Systems: Apple Mac OS X

Operating System Versions: Mac OS X version 10.4.9 (Tiger) or a later version of Mac OS

Note To verify that your computer meets these minimum requirements, on the Apple menu, click About This Mac.

Other requirements: To connect to a Windows-based computer, you must have network access and permissions to connect to a Windows-based computer that is running Terminal Services or Remote Desktop Services. These services are included with the following Windows products:

  • Windows XP Professional
  • Windows XP Media Center
  • Windows Server 2003
  • Windows Server 2003 Datacenter
  • Windows Server 2003 Enterprise
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Ultimate
  • Windows Server 2008
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise

Installing the Update

  1. Quit any applications that are running, including all Microsoft Office applications, Microsoft Messenger, and Office Notifications, because they might interfere with the installation.
  2. Make sure that your computer meets the minimum system requirements.
  3. Click Download, or click the link for the language version that you want.
  4. Follow the instructions on the screen to save the file to your hard disk. If you are using Safari, the downloaded file is saved to the desktop unless you specified a different location in the Preferences dialog box of Safari. To check your preferences, on the Safari menu, click Preferences, and then click General.
  5. Double-click the file you downloaded in step 4 to place the Remote Desktop Connection volume on your desktop, and then double-click the Remote Desktop Connection volume to open it. This step might have been performed for you.
  6. In the Remote Desktop Connection volume window, double-click the Remote Desktop Connection.mpkg application to start the update process, and then follow the instructions on the screen.
  7. If the installation finishes successfully, you can remove the update installer from your hard disk. To remove the update installer, first drag the Microsoft Remote Desktop Connection volume to the Trash, and then drag the file that you downloaded to the Trash.

Restart Requirement

This update does not require you to restart your computer.

Removing the Update

This security update cannot be uninstalled.

Additional Information

If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support to learn about the support options that are available to you.

Other Information

Acknowledgments

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

  • Wushi of Team509, working with Zero Day Initiative, for reporting the Remote Desktop Connection Heap Overflow Vulnerability (CVE-2009-1133)
  • Yamata Li of Palo Alto Networks for reporting the Remote Desktop Connection ActiveX Control Heap Overflow Vulnerability (CVE-2009-1929)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • 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 (August 11, 2009): Bulletin published.
  • V1.1 (August 13, 2009): Corrected update package and workaround information. See revision entry in the section, Frequently Asked Questions (FAQ) Related to This Security Update. This is an informational change only. Customers who have successfully installed updates for their systems do not need to reinstall.
  • V1.2 (August 19, 2009): Corrected the registry key verification entry for RDP Version 5.1 on Windows XP Service Pack 2 (KB958470).
  • V2.0 (August 25, 2009): Corrected the download link for RDP Version 5.2 for Windows XP Service Pack 2 (KB958469). Also corrected the footnote that prescribed an erroneous install sequence for KB958471 and KB958470. Customers who have successfully installed these updates do not need to reinstall.
  • V2.1 (November 4, 2009): Added a new known issues entry to the Frequently Asked Questions (FAQ) Related to This Security Update section.

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.