[THIN] ALERT: Microsoft Security Bulletin MS05-041

  • From: "Jim Kenzig Kenzig.com" <jkenzig@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx, neocug@xxxxxxxxxxxxx
  • Date: Wed, 10 Aug 2005 06:21:53 -0700 (PDT)

Microsoft Security Bulletin MS05-041Vulnerability in Remote Desktop Protocol 
Could Allow Denial of Service 
(899591)http://www.microsoft.com/technet/security/bulletin/MS05-041.mspx

Issued: August 9, 2005
Version: 1.0
sID='l1-EYAA'Summary
Who should read this document: System administrators who operate terminal 
servers that use Microsoft Windows 2000 or Windows Server 2003, system 
administrators who operate any system where Remote Desktop or Remote Web 
Workplace has been enabled, and system administrators who operate any system 
where Remote Assistance is in use.

Impact of Vulnerability: Denial of Service

Maximum Severity Rating: Moderate

Recommendation: We recommend that customers consider applying the security 
update.

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software: 
?
Microsoft Windows 2000 Server Service Pack 4 ? Download the update
?
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 ? 
Download the update
?
Microsoft Windows XP Professional x64 Edition ? Download the update
?
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 
? Download the update
?
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows 
Server 2003 with SP1 for Itanium-based Systems ? Download the update
?
Microsoft Windows Server 2003 x64 Edition ? Download the update

Non-Affected Software:
?
Microsoft Windows 2000 Professional Service Pack 4
?
Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft 
Windows Millennium Edition (ME)

The software in this list has been tested to determine whether the versions are 
affected. Other versions either no longer include security update support or 
may not be affected. To determine the support life cycle for your product and 
version, visit the Microsoft Support Lifecycle Web site.
Top of section

General InformationsID='3l1-EDXAA';writePM(sID)startA('s'+sID)Executive 
SummaryendA()chkHide('s'+sID);
Executive Summary:

This update resolves a newly-discovered, privately-reported vulnerability. A 
vulnerability in the Remote Desktop Protocol (RDP) exists that could allow an 
attacker to cause a system to stop responding. The vulnerability is documented 
in the ?Vulnerability Details? section of this bulletin.

We recommend that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:
Vulnerability IdentifiersImpact of VulnerabilityWindows 2000 ServerWindows 
XPWindows Server 2003
Remote Desktop Protocol Vulnerability - CAN-2005-1218

Denial of Service

Moderate

Moderate

Moderate


This assessment is based on the types of systems that are affected by the 
vulnerability, their typical deployment patterns, and the effect that 
exploiting the vulnerability would have on them.

Note The severity ratings for non-x86 operating system versions map to the x86 
operating systems versions as follows: 
?
The Microsoft Windows XP Professional x64 Edition severity rating is the same 
as the Windows XP Service Pack 2 severity rating.
?
The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is 
the same as the Windows Server 2003 severity rating.
?
The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity 
rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
?
The Microsoft Windows Server 2003 x64 Edition severity rating is the same as 
the Windows Server 2003 Service Pack 1 severity rating.

Top of section

sID='3l1-ECXAA';writePM(sID)startA('s'+sID)Frequently asked questions (FAQ) 
related to this security updateendA()chkHide('s'+sID);
Extended security update support for Microsoft Windows NT Workstation 4.0 
Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. 
Extended security update support for Microsoft Windows NT Server 4.0 Service 
Pack 6a ended on December 31, 2004. Extended security update support for 
Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I?m still using 
one of these operating systems, what should I do?

Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 
6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached 
the end of their life cycles. It should be a priority for customers who have 
these operating system versions to migrate to supported versions to prevent 
potential exposure to vulnerabilities. For more information about the Windows 
Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. 
For more information about the extended security update support period for 
these operating system versions, visit the Microsoft Product Support Services 
Web site. 

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

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

Security update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 
(Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium)ended 
on June 30, 2005.I?m still using one of these operating systems, what should I 
do?

With the release of Windows XP Professional x64 Edition, Microsoft Windows XP 
64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition 
Version 2003 (Itanium) will no longer receive security update support. It 
should be a priority for customers who have these operating system versions to 
migrate to supported versions to prevent potential exposure to vulnerabilities. 
Microsoft will continue to fully support Windows Server 2003 for Itanium-based 
systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 
Editions for 64-bit computing requirements. Microsoft continues to license and 
support Windows Server 2003 Enterprise and Datacenter editions for 
Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise 
Edition. In the future we will expand Itanium support to Visual Studio 2005, 
.NET Framework 2005 and SQL Server 2005.

Customers who require additional assistance about this issue must contact their 
Microsoft account team representative, their Technical Account Manager, or the 
appropriate Microsoft partner representative for information about the 
available migration options. Customers without an Alliance, Premier, or 
Authorized Contract can contact their local Microsoft sales office. For contact 
information, visit the Microsoft Worldwide Information Web site, select the 
country, and then click Go to see a list of telephone numbers. When you call, 
ask to speak with the local Premier Support sales manager. 

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine 
whether this update is required?

Yes. MBSA 1.2.1 will determine whether this update is required. For more 
information about MBSA, visit the MBSA Web site.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine 
whether this update is required?

Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can 
detect security updates for products that Microsoft Update supports. For more 
information about MBSA, visit the MBSA Web site.



Can I use Systems Management Server (SMS) to determine whether this update is 
required?

Yes. SMS can help detect and deploy this security update. For information about 
SMS, visit theSMS Web site. The Security Update Inventory Tool can be used by 
SMS for detecting security updates that are offered by Windows Update, that are 
supported by Software Update Services, and other security updates that are 
supported by MBSA 1.2.1. For more information about the Security Update 
Inventory Tool, see the following Microsoft Web site. For more information 
about the limitations of the Security Update Inventory Tool, see Microsoft 
Knowledge Base Article 306460. The SMS 2003 Inventory Tool for Microsoft 
Updates can be used by SMS for detecting security updates that are offered by 
Microsoft Update and that are supported by Windows Server Update Services. For 
more information about the SMS 2003 Inventory Tool for Microsoft Updates, see 
the following Microsoft Web site.



Top of section

sID='3l1-EBXAA';writePM(sID)startA('s'+sID)Vulnerability 
DetailsendA()chkHide('s'+sID);sID='3l2-EABXAA';writePM(sID)startA('s'+sID)Remote
 Desktop Protocol Vulnerability - CAN-2005-1218:endA()chkHide('s'+sID);
A denial of service vulnerability exists that could allow an attacker to send a 
specially crafted Remote Data Protocol (RDP) message to an affected system. An 
attacker could cause this system to stop responding.
sID='3l3-ECABXAA';writePM(sID)startA('s'+sID)Mitigating Factors for Remote 
Desktop Protocol Vulnerability - CAN-2005-1218:endA()chkHide('s'+sID);?
Firewall best practices and standard default firewall configurations can help 
protect networks from attacks that originate outside the enterprise perimeter. 
Best practices recommend that systems that are connected to the Internet have a 
minimal number of ports exposed. 
?
By default, the Remote Desktop Protocol (RDP) is not enabled on any operating 
system version. On Windows XP and Windows Server 2003, Remote Assistance can 
enable RDP. On Windows XP Media Center Edition, RDP is enabled if a Media 
Center Extender has been installed. For information about Media Center 
Extenders, visit the following Web site.

On Small Business Server 2000 and on Windows Small Business Server 2003, RDP in 
enabled by default. However, by default, on Windows Small Business Server 2003 
and earlier, the RDP Protocol communication ports are blocked from the 
Internet. RDP is available only on the local network unless Terminal Services 
or the Remote Web Workplace features have been enabled by using the Configure 
E-mail and Internet Connection Wizard (CEICW).
?
If Remote Desktop is manually enabled, the following Windows Firewall changes 
will occur, depending on the operating system version:
?
On Windows XP Service Pack 2 systems that have the Windows Firewall enabled, 
enabling the Remote Desktop feature will automatically enable the Remote 
Desktop exception in the firewall, with the scope of All computers (including 
those on the Internet). When you disable Remote Desktop, this firewall 
exception is automatically disabled.

On Windows XP Service Pack 1, Windows Server 2003, and Windows Server 2003 
Service Pack 1, enabling the Remote Desktop Feature does not enable the Remote 
Desktop exception in the firewall. Enabling Remote Desktop causes a dialog box 
that indicates that you must manually enable this exception. There is a Remote 
Desktop entry in the exception in the list of the firewall exceptions that a 
user would have to manually enable. Disabling Remote Desktop does not change 
the exception status in the firewall. However, although the system is no longer 
vulnerable to this issue through Remote Desktop, it could still be vulnerable 
through Remote Assistance and Terminal Services, where available.

Top of section

sID='3l3-EBABXAA';writePM(sID)startA('s'+sID)Workarounds for Remote Desktop 
Protocol Vulnerability - CAN-2005-1218:endA()chkHide('s'+sID);
Microsoft has tested the following workarounds. While these workarounds will 
not correct the underlying vulnerability, they help block known attack vectors. 
When a workaround reduces functionality, it is identified in the following 
section.
?
Disable Terminal Services, Remote Desktop, Remote Assistance, and Windows Small 
Business Server 2003 Remote Web Workplace feature if they are no longer 
required.

If you no longer need these services on your system, consider disabling them as 
a security best practice. Disabling unused and unneeded services helps reduce 
your exposure to security vulnerabilities. 

For information about how to disable Remote Desktop manually, visit the 
following Web site.

For information about how to disable Remote Desktop by using Group Policy, see 
the following Microsoft Knowledge Base Article.

For information about Remote Assistance, including instructions on how to 
disable Remote Assistance manually and by using Group Policy, visit the 
following Web site.

For information about how to disable the Windows Small Business Server 2003 
Terminal Services and Remote Web Workplace features, visit the following Web 
site.
?
Block TCP port 3389 at the enterprise perimeter firewall:

This port is used to initiate a connection with the affected component. 
Blocking it at the network perimeter firewall will help protect systems that 
are behind that firewall from attempts to exploit this vulnerability. This can 
help protect networks from attacks that originate outside the enterprise 
perimeter. Blocking the affected ports at the enterprise perimeter is the best 
defense to help avoid Internet-based attacks. However, systems could still be 
vulnerable to attacks from within their enterprise perimeter. Additionally, on 
Windows XP and Windows Server 2003, the Windows Firewall can help protect 
individual systems. By default, the Windows Firewall does not allow connections 
to this port, except in Windows XP Service Pack 2 when the Remote Desktop 
feature is enabled. For information about how to disable the Windows Firewall 
exception for Remote Desktop on these platforms, visit the following Web site. 
If you cannot disable the Windows Firewall exception for Remote Desk
 top, you
 may be able to reduce the scope of this vulnerability by setting the default 
value of All computers (Including those on the Internet), to the local network. 
Doing this helps reduce the likelihood of attacks from the Internet.

Note Windows Small Business Server 2003 uses a feature named Remote Web 
Workplace. This feature uses TCP port 4125 to listen for RDP connections. If 
you are using this feature, you should validate that this port is also blocked 
from the Internet in addition to port 3389.

Note It is possible to manually change the affected components to use other 
ports. If you have performed these actions, you should also block those 
additional ports.
?
Help secure Remote Desktop Connections by using an IPsec policy.

Specific configurations would be dependent upon the individual environment. For 
information about Internet Protocol Security (IPsec), visit the following Web 
site. Detailed information about IPsec and about how to apply filters is 
available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge 
Base Article 813878.
?
Help secure Remote Desktop Connections by using a virtual private network (VPN) 
connection.

Specific configurations depend on the individual environment. For information 
about Virtual Private Networks, visit the following Web site.

Top of section

sID='3l3-EAABXAA';writePM(sID)startA('s'+sID)FAQ for Remote Desktop Protocol 
Vulnerability - CAN-2005-1218:endA()chkHide('s'+sID);
What is the scope of the vulnerability?

This is a denial of service vulnerability. An attacker who exploited this 
vulnerability could cause the affected system to stop responding and 
automatically restart. During that time, the server could not respond to 
requests. The denial of service vulnerability would not allow an attacker to 
execute code or to elevate their user rights, but it could cause the affected 
system to stop accepting requests.

What causes the vulnerability?
The process used to validate data by the Remote Desktop Protocol.

What is Remote Desktop Protocol (RDP)?
Remote Desktop Protocol (RDP) lets users create a virtual session on their 
desktop computers. It allows remote users to access all the data and 
applications on their computers. For more information about RDP, visit the 
following Web site.

In which Microsoft products is RDP implemented?
In general, RDP is the underlying protocol for Windows features that allow 
remote desktop sessions. These features include:
?
Terminal Services in Windows 2000 and in Windows Server 2003 implement RDP. For 
more information about Terminal Services and RDP, visit the following Web site.
?
Remote Desktop in Windows XP implements RDP. For more information about the 
Remote Desktop feature in Windows XP, visit the following Web site.
?
Creating a Remote Assistance request in Windows XP and Windows Server 2003 
enables RDP until a short time after the request expires. For information about 
Remote Assistance, including instructions on how to disable Remote Assistance 
manually and by using Group Policy, visit the following Web site.
?
Media Center Extenders on Windows XP Media Center Edition 2005 systems enable 
RDP. For information about Media Center Extenders, visit the following Web 
site. For detailed technical information about Media Center Extenders, visit 
the following Web site. The Media Center Extenders can use RDP over ports 
beyond the default TCP 3389 port. 
?
Remote Web Workplace in Windows Small Business Server 2003 enables RDP. For 
more information about this feature, see the following TechNet Support WebCast. 
For information about how to disable the Windows Small Business Server 2003 
Remote Web Workplace feature, visit the following Web site. The Remote Web 
Workplace feature will use RDP over ports beyond the default TCP 3389 port.

Is RDP enabled by default in Windows?
No. By default, the Remote Desktop Protocol (RDP) is not enabled on any 
operating system version. On some versions of Windows XP Media Center Edition, 
RDP is enabled if a Media Center Extender has been installed. For information 
about Media Center Extenders, visit the following Web site. For detailed 
technical information about Media Center Extenders, visit the following Web 
site.

Small Business Server 2000 and Windows Small Business Server 2003 enable RDP by 
default. However, by default, on Windows Small Business Server 2003 and 
earlier, the RDP Protocol communication ports are blocked from the Internet and 
RDP is available only on the local network, unless Terminal Services or Remote 
Web Workplace has been enabled by using the Configure E-mail and Internet 
Connection Wizard (CEICW).

Windows XP Home Edition does not support Remote Desktop. However, it does 
support Remote Assistance. Remote Assistance enables RDP until a short time 
after the Remote Assistance request expires. During this time, Windows XP Home 
systems could be vulnerable to this issue if they allow the Remote Desktop 
exception through the Windows Firewall.

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

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

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially 
crafted message and sending the message to an affected system. Receipt of such 
a message could cause the vulnerable system to fail in such a way that it could 
cause a denial of service.

What systems are primarily at risk from the vulnerability?
Windows 2000 Server-based terminal servers and Windows Server 2003-based 
terminal servers are primarily at risk from this vulnerability. Administrators 
must manually configure these operating system versions to enable the Terminal 
Server features to become vulnerable to this issue. Windows Small Business 
Server 2003-based servers are also at risk if the administrator has used the 
Configure E-mail and Internet Connection Wizard to enable Terminal Services or 
the Remote Web Workplace connections to the server from the Internet. Windows 
XP and Windows Server 2003 systems are at risk if they have manually enabled 
Remote Desktop or are using Remote Assistance. Windows 2000 Professional does 
not contain support for the RDP protocol and is not vulnerable to this issue.

Could the vulnerability be exploited over the Internet? 
Yes. An attacker could try to exploit this vulnerability over the Internet. 
Firewall best practices and standard default firewall configurations can help 
protect against attacks that originate from the Internet. Microsoft has 
provided information about how you can help protect your PC. End users can 
visit the Protect Your PC Web site. IT professionals can visit the Security 
Guidance Center Web site.

What does the update do?
The update removes the vulnerability by modifying the way that RDP validates 
the length of a message before reading the message.

When this security bulletin was issued, had this vulnerability been publicly 
disclosed?
Yes. This vulnerability has been publicly disclosed. 

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.

Does applying this security update help protect customers from the 
vulnerability details that had been published publicly?
Yes. This security update addresses the vulnerability details that have been 
published on this issue.

Top of section


Top of section


Top of section

sID='3l1-EAXAA';writePM(sID)startA('s'+sID)Security Update 
InformationendA()chkHide('s'+sID);
Affected Software:

For information about the specific security update for your affected software, 
click the appropriate link:
sID='3l2-EEAXAA';writePM(sID)startA('s'+sID)Windows Server 2003 (all 
versions)endA()chkHide('s'+sID);
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 
Service Pack 1.

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

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/overwriteoem

Overwrites OEM files without prompting

/nobackup

Does not back up files needed for uninstall

/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files

/integrate:path

Integrates the update into the Windows source files. These files are located at 
the path that is specified in the switch.

/extract[:path]

Extracts files without starting the Setup program

/ER

Enables extended error reporting

/verbose

Enables verbose logging. During installation, creates %Windir%\CabBuild.log. 
This log details the files that are copied. Using this switch may cause the 
installation to proceed more slowly.


Note You can combine these switches into one command. For backward 
compatibility, the security update also supports many of the setup switches 
that the earlier version of the Setup program uses. For more information about 
the supported installation switches, see Microsoft Knowledge Base Article 
262841. For more information about the Update.exe installer, visit the 
Microsoft TechNet Web site.

Deployment Information

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

Windowsserver2003-kb899591-x86-enu /quiet

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

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

Windowsserver2003-kb899591-x86-enu /norestart

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

Restart Requirement

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

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this 
security update. The Spuninst.exe utility is located in the 
%Windir%\$NTUninstallKB899591$\Spuninst folder.
Supported Spuninst.exe SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files


File Information

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

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; 
Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise 
Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition 
with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, 
Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with 
SP1:
File NameVersionDateTimeSizeFolder
Rdpwd.sys

5.2.3790.348

15-Jun-2005

15:13

123,016

RTMGDR

Rdpwd.sys

5.2.3790.348

15-Jun-2005

15:25

123,016

RTMQFE

Rdpwd.sys

5.2.3790.2465

15-Jun-2005

15:33

158,344

SP1GDR

Rdpwd.sys

5.2.3790.2465

15-Jun-2005

15:38

152,200

SP1QFE

Arpidfix.exe

5.2.3790.2477

30-Jun-2005

00:44

32,256




Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows 
Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, 
Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, 
Datacenter Edition with SP1 for Itanium-based Systems:
File NameVersionDateTimeSizeCPUFolder
Rdpwd.sys

5.2.3790.348

01-Jul-2005

23:27

370,312

IA-64

RTMGDR

Rdpwd.sys

5.2.3790.348

01-Jul-2005

23:27

370,312

IA-64

RTMQFE

Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

477,832

IA-64

SP1GDR

Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

477,832

IA-64

SP1QFE

Arpidfix.exe

5.2.3790.2477

01-Jul-2005

23:27

74,752

IA-64




Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 
Edition; and Windows Server 2003, Datacenter x64 Edition:
File NameVersionDateTimeSizeCPUFolder
Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

230,024

x64

SP1GDR

Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

230,024

x64

SP1QFE

Arpidfix.exe

5.2.3790.2477

01-Jul-2005

23:27

43,008

x64




Notes When you install these security updates, the installer checks to see if 
one or more of the files that are being updated on your system have previously 
been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the 
installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, 
the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. 
Security updates may not contain all variations of these files. For more 
information about this behavior, see Microsoft Knowledge Base Article 824994.

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

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

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

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

Verifying that the Update Has Been Applied
?
Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you 
may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA 
allows administrators to scan local and remote systems for missing security 
updates and for common security misconfigurations. For more information about 
MBSA, visit the Microsoft Baseline Security Analyzer Web site.
?
File Version Verification

Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.

1.

Click Start, and then click Search.

2.

In the Search Results pane, click All files and folders under Search Companion.

3.

In the All or part of the file name box, type a file name from the appropriate 
file information table, and then click Search.

4.

In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties. 

Note Depending on the version of the operating system or programs installed, 
some of the files that are listed in the file information table may not be 
installed.

5.

On the Version tab, determine the version of the file that is installed on your 
computer by comparing it to the version that is documented in the appropriate 
file information table.

Note Attributes other than the file version may change during installation. 
Comparing other file attributes to the information in the file information 
table is not a supported method of verifying that the update has been applied. 
Also, in certain cases, files may be renamed during installation. If the file 
or version information is not present, use one of the other available methods 
to verify update installation.
?
Registry Key Verification

You may also be able to verify the files that this security update has 
installed by reviewing the following registry keys.

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 
2003\SP2\KB899591\Filelist

Note This registry key may not contain a complete list of installed files. 
Also, this registry key may not be created correctly if an administrator or an 
OEM integrates or slipstreams the 899591 security update into the Windows 
installation source files.

Top of section



sID='3l2-ECAXAA';writePM(sID)startA('s'+sID)Windows XP (all 
versions)endA()chkHide('s'+sID);
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later 
version. For more information, see Microsoft Knowledge Base Article 322389.

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

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/overwriteoem

Overwrites OEM files without prompting

/nobackup

Does not back up files needed for uninstall

/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files

/integrate:path

Integrates the update into the Windows source files. These files are located at 
the path that is specified in the switch.

/extract[:path]

Extracts files without starting the Setup program

/ER

Enables extended error reporting

/verbose

Enables verbose logging. During installation, creates %Windir%\CabBuild.log. 
This log details the files that are copied. Using this switch may cause the 
installation to proceed more slowly.


Note You can combine these switches into one command. For backward 
compatibility, the security update also supports the setup switches that the 
earlier version of the Setup program uses. For more information about the 
supported installation switches, see Microsoft Knowledge Base Article 262841. 
For more information about the Update.exe installer, visit the Microsoft 
TechNet Web site.

Deployment Information

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

Windowsxp-kb899591-x86-enu /quiet

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

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

Windowsxp-kb899591-x86-enu /norestart

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

Restart Requirement

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

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this 
security update. The Spuninst.exe utility is located in the 
%Windir%\$NTUninstallKB899591$\Spuninst folder.
Supported Spuninst.exe SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files


File Information

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

Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, 
Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home 
Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP 
Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
File NameVersionDateTimeSizeFolder
Rdpwd.sys

5.1.2600.1698

10-Jun-2005

04:30

116,104

SP1QFE

Rdpwd.sys

5.1.2600.2695

10-Jun-2005

04:09

139,528

SP2GDR

Rdpwd.sys

5.1.2600.2695

10-Jun-2005

04:06

139,528

SP2QFE

Arpidfix.exe

5.1.2600.2710

29-Jun-2005

23:54

30,720




Windows XP Professional x64 Edition:
File NameVersionDateTimeSizeCPUFolder
Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

230,024

x64

SP1GDR

Rdpwd.sys

5.2.3790.2465

01-Jul-2005

23:27

230,024

x64

SP1QFE

Arpidfix.exe

5.2.3790.2477

01-Jul-2005

23:27

43,008

x64




Notes When you install these security updates, the installer checks to see if 
one or more of the files that are being updated on your system have previously 
been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the 
installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, 
the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. 
Security updates may not contain all variations of these files. For more 
information about this behavior, see Microsoft Knowledge Base Article 824994.

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

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

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

Verifying that the Update Has Been Applied
?
Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you 
may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA 
allows administrators to scan local and remote systems for missing security 
updates and for common security misconfigurations. For more information about 
MBSA, visit the Microsoft Baseline Security Analyzer Web site.
?
File Version Verification

Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.

1.

Click Start, and then click Search.

2.

In the Search Results pane, click All files and folders under Search Companion.

3.

In the All or part of the file name box, type a file name from the appropriate 
file information table, and then click Search.

4.

In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties. 

Note Depending on the version of the operating system or programs installed, 
some of the files that are listed in the file information table may not be 
installed.

5.

On the Version tab, determine the version of the file that is installed on your 
computer by comparing it to the version that is documented in the appropriate 
file information table.

Note Attributes other than the file version may change during installation. 
Comparing other file attributes to the information in the file information 
table is not a supported method of verifying that the update has been applied. 
Also, in certain cases, files may be renamed during installation. If the file 
or version information is not present, use one of the other available methods 
to verify update installation.
?
Registry Key Verification

You may also be able to verify the files that this security update has 
installed by reviewing the following registry keys.

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB899591\Filelist

For Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 
2003\SP2\KB899591\Filelist

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

Top of section



sID='3l2-EAAXAA';writePM(sID)startA('s'+sID)Windows 2000 Server (all 
versions)endA()chkHide('s'+sID);
Prerequisites
For Windows 2000 Server, this security update requires Service Pack 4 (SP4). 
For Small Business Server 2000, this security update requires Small Business 
Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with 
Windows 2000 Server Service Pack 4 (SP4).

The software that is listed has been tested to determine whether the versions 
are affected. Other versions either no longer include security update support 
or may not be affected. To determine the support life cycle for your product 
and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft 
Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/overwriteoem

Overwrites OEM files without prompting

/nobackup

Does not back up files needed for uninstall

/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files

/integrate:path

Integrates the update into the Windows source files. These files are located at 
the path that is specified in the switch.

/extract[:path]

Extracts files without starting the Setup program

/ER

Enables extended error reporting

/verbose

Enables verbose logging. During installation, creates %Windir%\CabBuild.log. 
This log details the files that are copied. Using this switch may cause the 
installation to proceed more slowly.


Note You can combine these switches into one command. For backward 
compatibility, the security update also supports the setup switches that the 
earlier version of the Setup program uses. For more information about the 
supported installation switches, see Microsoft Knowledge Base Article 262841. 
For more information about the Update.exe installer, visit the Microsoft 
TechNet Web site. For more information about the terminology that appears in 
this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Deployment Information

To install the security update without any user intervention, use the following 
command at a command prompt for Windows 2000 Service Pack 4:

Windows2000-kb899591-x86-enu /quiet

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

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

Windows2000-kb899591-x86-enu /norestart

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

Restart Requirement

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

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this 
security update. The Spuninst.exe utility is located in the 
%Windir%\$NTUninstallKB899591$\Spuninst folder.
Supported Spuninst.exe SwitchesSwitchDescription
/help

Displays the command-line options
Setup Modes 
/passive

Unattended Setup mode. No user interaction is required, but installation status 
is displayed. If a restart is required at the end of Setup, a dialog box will 
be presented to the user with a timer warning that the computer will restart in 
30 seconds.

/quiet

Quiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestart

Does not restart when installation has completed

/forcerestart

Restarts the computer after installation and force other applications to close 
at shutdown without saving open files first.

/warnrestart[:x]

Presents a dialog box with a timer warning the user that the computer will 
restart in x seconds. (The default setting is 30 seconds.) Intended for use 
with the /quiet switch or the /passive switch.

/promptrestart

Display a dialog box prompting the local user to allow a restart
Special Options 
/forceappsclose

Forces other programs to close when the computer shuts down

/log:path

Allows the redirection of installation log files


File Information

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

Windows 2000 Server Service Pack 4 and Small Business Server 2000:
File NameVersionDateTimeSize
Rdpwd.sys

5.0.2195.7055

29-Jun-2005

08:49

90,296


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. MBSA 
allows administrators to scan local and remote systems for missing security 
updates and for common security misconfigurations. For more information about 
MBSA, visit the Microsoft Baseline Security Analyzer Web site.
?
File Version Verification

Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.

1.

Click Start, and then click Search.

2.

In the Search Results pane, click All files and folders under Search Companion.

3.

In the All or part of the file name box, type a file name from the appropriate 
file information table, and then click Search.

4.

In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties. 

Note Depending on the version of the operating system or programs installed, 
some of the files that are listed in the file information table may not be 
installed.

5.

On the Version tab, determine the version of the file that is installed on your 
computer by comparing it to the version that is documented in the appropriate 
file information table.

Note Attributes other than the file version may change during installation. 
Comparing other file attributes to the information in the file information 
table is not a supported method of verifying that the update has been applied. 
Also, in certain cases, files may be renamed during installation. If the file 
or version information is not present, use one of the other available methods 
to verify update installation.
?
Registry Key Verification

You may also be able to verify the files that this security update has 
installed by reviewing the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB899591\Filelist

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

Top of section


Top of section



Acknowledgments

Microsoft thanks the following for working with us to help protect customers:
?
Tom Ferris of Security Protocols for reporting the Remote Desktop Protocol 
Vulnerability (CAN-2005-1218).

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:
?
Security updates are available in the Microsoft Download Center. You can find 
them most easily by doing a keyword search for "security_patch."
?
Updates for consumer platforms are available at the Windows Update Web site. 

Support: 
?
Customers in the U.S. and Canada can receive technical support from Microsoft 
Product Support Services at 1-866-PCSAFETY. There is no charge for support 
calls that are associated with security updates.
?
International customers can receive support from their local Microsoft 
subsidiaries. There is no charge for support that is associated with security 
updates. For more information about how to contact Microsoft for support 
issues, visit the International Support Web site.

Security Resources: 
?
The Microsoft TechNet Security Web site provides additional information about 
security in Microsoft products. 
?
Microsoft Software Update Services
?
Microsoft Windows Server Update Services
?
Microsoft Baseline Security Analyzer (MBSA) 
?
Windows Update
?
Microsoft Update
?
Windows Update Catalog: For more information about the Windows Update Catalog, 
see Microsoft Knowledge Base Article 323166.
?
Office Update 

Software Update Services:

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

For more information about how to deploy security updates by using Software 
Update Services, visit the Software Update Services Web site. 

Windows Server Update Services:

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

For more information about how to deploy security updates using Windows Server 
Update Services, visit the Windows Server Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly-configurable 
enterprise solution for managing updates. By using SMS, administrators can 
identify Windows-based systems that require security updates and can perform 
controlled deployment of these updates throughout the enterprise with minimal 
disruption to end users. For more information about how administrators can use 
SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch 
Management Web site. SMS 2.0 users can also use Software Updates Service 
Feature Pack to help deploy security updates. For information about SMS, visit 
the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office 
Detection Tool, and the Enterprise Update Scanning Tool to provide broad 
support for security bulletin update detection and deployment. Some software 
updates may not be detected by these tools. Administrators can use the 
inventory capabilities of the SMS in these cases to target updates to specific 
systems. For more information about this procedure, visit the following Web 
site. Some security updates require administrative rights following a restart 
of the system. Administrators can use the Elevated Rights Deployment Tool 
(available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 
Administration Feature Pack) to install these updates.

Disclaimer: 

The information provided in the Microsoft Knowledge Base is provided "as is" 
without warranty of any kind. Microsoft disclaims all warranties, either 
express or implied, including the warranties of merchantability and fitness for 
a particular purpose. In no event shall Microsoft Corporation or its suppliers 
be liable for any damages whatsoever including direct, indirect, incidental, 
consequential, loss of business profits or special damages, even if Microsoft 
Corporation or its suppliers have been advised of the possibility of such 
damages. Some states do not allow the exclusion or limitation of liability for 
consequential or incidental damages so the foregoing limitation may not apply.

Revisions: 
?
V1.0 (August 9, 2005): Bulletin published

Other related posts: