Security Bulletin
Microsoft Security Bulletin MS06-025 - Critical
Vulnerability in Routing and Remote Access Could Allow Remote Code Execution (911280)
Published: June 13, 2006 | Updated: June 27, 2006
Version: 2.0
Summary
Who Should Read this Document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately.
Security Update Replacement: None
Caveats: Microsoft Knowledge Base Article 911280 documents the currently known issues that customers may experience when they install this security update.
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows 2000 Service Pack 4 — Download the update
- Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 — Download the update
- Microsoft Windows XP Professional x64 Edition — Download the update
- Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 — Download the update
- Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems — Download the update
- Microsoft Windows Server 2003 x64 Edition — Download the update
Non-Affected Software:
- Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (Me)
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
General Information
Executive Summary
Executive Summary:
This update resolves several newly discovered, privately reported vulnerability. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section of this bulletin.
We recommend that customers apply the update immediately
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 2000 | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
|---|---|---|---|---|---|---|
| RASMAN Memory Corruption Vulnerability - CVE-2006-2370 | Remote Code Execution | Critical | Important | Important | Important | Important |
| RASMAN Registry Corruption Vulnerability - CVE-2006-2371 | Remote Code Execution | Critical | Important | Important | Important | Important |
| Aggregate Severity of All Vulnerabilities | Critical | Important | Important | Important | Important |
This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.
Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
- The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
- The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
- The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
- The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
Frequently Asked Questions (FAQ) Related to This Security Update
Why did Microsoft reissue this bulletin on June 27, 2006?
Microsoft updated this bulletin and the associated security updates to address the issues identified in Microsoft Knowledge Base Article 911280. Only customers who use dial-up connections that use scripts that configure their device for parity, stop bits or data bits or a post-connect terminal window or dial-up scripting, are affected by the issues identified in the KB article.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.
Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
No. Windows 98, on Windows 98 Second Edition, or on Windows Millennium Edition do not contain the affected component.
Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Customers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 1.2.1 | MBSA 2.0 |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
| Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 | Yes | Yes |
| Microsoft Windows XP Professional x64 Edition | No | Yes |
| Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 | Yes | Yes |
| Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems | No | Yes |
| Microsoft Windows Server 2003 x64 Edition family | No | Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660
Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
| Software | SMS 2.0 | SMS 2003 |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
| Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 | Yes | Yes |
| Microsoft Windows XP Professional x64 Edition | No | Yes |
| Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 | Yes | Yes |
| Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems | No | Yes |
| Microsoft Windows Server 2003 x64 Edition family | No | Yes |
SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to software that MBSA does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates 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 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
Vulnerability Details
RASMAN Memory Corruption Vulnerability - CVE-2006-2370
There is a remote code execution vulnerability in the Remote Access Connection Manager (RASMAN) service that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.
Mitigating factors for RASMAN Memory Corruption Vulnerability - CVE-2006-2370:
- The Remote Access Connection Manager service is not started by default for all supported Microsoft Windows operating systems with the exception of Microsoft Windows 2000 Service Pack 4. The only service dependent upon the Remote Access Connection Manager service is the Remote Access Auto Connection Manager. For Microsoft Windows 2000, the Internet Connection Sharing service depends on the Remote Access Connection Manager service. Enabling a dependent service could cause the Remote Access Connection Manager service to start.
- On Windows XP Service Pack 2 and Windows Server 2003 systems, an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely by anonymous users or by users who have standard user accounts. However, the affected component is available remotely to users who have administrative permissions.
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
Workarounds for RASMAN Memory Corruption Vulnerability- CVE-2006-2370:
Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
Disable the Remote Access Connection Manager service
Disabling the Remote Access Connection Manager service will help protect the affected system from attempts to exploit this vulnerability. To disable the Remote Access Connection Manager (RASMAN) service, follow these steps:
- Click Start, and then click Control Panel. Alternatively, point to Settings, and then click Control Panel.
- Double-click Administrative Tools.
- Double-click Services.
- Double-click Remote Access Connection Manager
- In the Startup type list, click Disabled.
- Click Stop, and then click OK.
You can also stop and disable the Remote Access Connection Manager (RASMAN) service by using the following command at the command prompt:
sc stop rasman & sc config rasman start= disabledImpact of Workaround: If you disable the Remote Access Connection Manager service, you cannot offer routing services to other hosts in local area and wide area network environments. Therefore, we recommend this workaround only on systems that do not require the use of RASMAN for remote access and routing.
Block the following at the firewall:
- UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and 593
- All unsolicited inbound traffic on ports greater than 1024
- Any other specifically configured RPC port
These ports are used to initiate a connection with RPC. Blocking them at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Also, make sure that you block any other specifically configured RPC port on the remote system. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports that RPC uses, visit the following Web site.
To help protect from network-based attempts to exploit this vulnerability, use a personal firewall, such as the Internet Connection Firewall, which is included with Windows XP and with Windows Server 2003.
By default, the Internet Connection Firewall feature in Windows XP and in Windows Server 2003 helps protect your Internet connection by blocking unsolicited incoming traffic. We recommend that you block all unsolicited incoming communication from the Internet. In Windows XP Service Pack 2 this features is called the Windows Firewall.To enable the Internet Connection Firewall feature by using the Network Setup Wizard, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Network and Internet Connections, and then click Setup or change your home or small office network. The Internet Connection Firewall feature is enabled when you select a configuration in the Network Setup Wizard that indicates that your system is connected directly to the Internet.
To configure Internet Connection Firewall manually for a connection, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Networking and Internet Connections, and then click Network Connections.
- Right-click the connection on which you want to enable Internet Connection Firewall, and then click Properties.
- Click the Advanced tab.
- Click to select the Protect my computer or network by limiting or preventing access to this computer from the Internet check box, and then click OK.
Note If you want to enable certain programs and services to communicate through the firewall, click Settings on the Advanced tab, and then select the programs, the protocols, and the services that are required.
To help protect from network-based attempts to exploit this vulnerability, enable advanced TCP/IP filtering on systems that support this feature.
You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.To help protect from network-based attempts to exploit this vulnerability, block the affected ports by using IPSec on the affected systems.
Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.
FAQ for RASMAN Memory Corruption Vulnerability - CVE-2006-2370:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
An unchecked buffer in Routing and Remote Access technologies specifically affecting the Remote Access Connection Manager Service.
What are RRAS, RAS and RASMAN?
RRAS makes it possible for a computer to function as a network router. RRAS also provides the next generation of server functionality for the Remote Access Service (RAS) for Windows. The RRAS server functionality follows and builds upon the Remote Access Service (RAS) that was included in previous operating systems
The Remote Access Service lets users connect to a remote computer over phone lines, so they can work as if their system were physically connected to the remote network. These services enable remote users to do activities such as send and receive e-mail, fax documents, retrieve files, and print documents on an office printer. The Remote Access Service is a native service in Windows 2000, Windows XP and Windows Server 2003.
The Remote Access Connection Manager is a service that handles the details of establishing the connection to the remote server. This service also provides the client with status information during the connection operation. The Remote Access Connection Manager starts automatically when an application loads the RASAPI32.DLL
Why was RRAS Memory Corruption Vulnerability - CVE 2206-2370 changed to RASMAN Memory Corruption Vulnerability - CVE 2206-2370?
The Vulnerability Details section was updated and the specific vulnerability renamed to more accurately reflect the affected component.
Which RRAS component is affected?
While RRAS can be considered a class of technologies, this update specifically addresses vulnerabilities identified with the Remote Access Connection Manager Service also known as RASMAN. For additional information on RRAS and RRAS related technologies please see the following MSDN article on Routing and Remote Access.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
Who could exploit the vulnerability?
On Windows 2000 Service Pack 4 and Windows XP Service Pack 1, any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability. In order to exploit the vulnerability on Windows XP Service Pack 2 and Windows Server 2003, an attacker must have valid login credentials to a target system.
How could an attacker exploit the vulnerability?
An attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component either locally or remotely.
What systems are primarily at risk from the vulnerability?
Microsoft Windows 2000, Windows XP and Windows Server 2003 are primarily at risk from this vulnerability. Systems that use Internet Connection Sharing or applications that call RASAPI32.dll are at risk as they cause the Remote Access Connection Manager to load automatically..
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.
Could the vulnerability be exploited over the Internet?
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 validating the way that Routing and Remote Access handles RPC related requests.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
RASMAN Registry Corruption Vulnerability - CVE-2006-2371
There is a remote code execution vulnerability in the Remote Access Connection Manager (RASMAN) Service that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system
Mitigating Factors for RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
- The Remote Access Connection Manager service is not started by default for all supported Microsoft Windows operating systems with the exception of Microsoft Windows 2000 Service Pack 4. The only service dependent upon the Remote Access Connection Manager service is the Remote Access Auto Connection Manager. For Microsoft Windows 2000, the Internet Connection Sharing service depends on the Remote Access Connection Manager service. Enabling a dependent service could cause the Remote Access Connection Manager service to start.
- On Windows XP Service Pack 2 and Windows Server 2003 systems, an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely by anonymous users or by users who have standard user accounts. However, the affected component is available remotely to users who have administrative permissions
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
Workarounds for RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
Disable the Remote Access Connection Manager service.
Disabling the Remote Access Connection Manager service will help protect the affected system from attempts to exploit this vulnerability. To disable the Remote Access Connection Manager Service, follow these steps:
- Click Start, and then click Control Panel. Alternatively, point to Settings, and then click Control Panel.
- Double-click Administrative Tools.
- Double-click Services.
- Double-click Remote Access Connection Manager
- In the Startup type list, click Disabled.
- Click Stop, and then click OK.
You can also stop and disable the Remote Access Connection Manager service by using the following command at the command prompt:
sc stop rasman & sc config rasman start= disabled
Impact of Workaround: If you disable the Remote Access Connection Manager service, you cannot offer routing services to other hosts in local area and wide area network environments. Therefore, we recommend this workaround only on systems that do not require the use of RRAS for remote access and routing.
To help protect from network-based attempts to exploit this vulnerability, use a personal firewall, such as the Internet Connection Firewall, which is included with Windows XP and with Windows Server 2003.
By default, the Internet Connection Firewall feature in Windows XP and in Windows Server 2003 helps protect your Internet connection by blocking unsolicited incoming traffic. We recommend that you block all unsolicited incoming communication from the Internet. In Windows XP Service Pack 2 this features is called the Windows Firewall.To enable the Internet Connection Firewall feature by using the Network Setup Wizard, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Network and Internet Connections, and then click Setup or change your home or small office network. The Internet Connection Firewall feature is enabled when you select a configuration in the Network Setup Wizard that indicates that your system is connected directly to the Internet.
To configure Internet Connection Firewall manually for a connection, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Networking and Internet Connections, and then click Network Connections.
- Right-click the connection on which you want to enable Internet Connection Firewall, and then click Properties.
- Click the Advanced tab.
- Click to select the Protect my computer or network by limiting or preventing access to this computer from the Internet check box, and then click OK.
Note If you want to enable certain programs and services to communicate through the firewall, click Settings on the Advanced tab, and then select the programs, the protocols, and the services that are required.
To help protect from network-based attempts to exploit this vulnerability, enable advanced TCP/IP filtering on systems that support this feature.
You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.To help protect from network-based attempts to exploit this vulnerability, block the affected ports by using IPSec on the affected systems.
Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.Block the following at the firewall:
- UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and 593
- All unsolicited inbound traffic on ports greater than 1024
- Any other specifically configured RPC port
These ports are used to initiate a connection with RPC. Blocking them at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Also, make sure that you block any other specifically configured RPC port on the remote system. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports that RPC uses, visit the following Web site.
FAQ for RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
An unchecked buffer in Routing and Remote Access technologies specifically affecting the Remote Access Connection Manager Service.
What are RRAS, RAS and RASMAN?
RRAS makes it possible for a computer to function as a network router. RRAS also provides the next generation of server functionality for the Remote Access Service (RAS) for Windows. The RRAS server functionality follows and builds upon the Remote Access Service (RAS) that was included in previous operating systems.
The Remote Access Service lets users connect to a remote computer over phone lines, so they can work as if their system were physically connected to the remote network. These services enable remote users to do activities such as send and receive e-mail, fax documents, retrieve files, and print documents on an office printer. The Remote Access Service is a native service in Windows 2000, Windows XP and Windows Server 2003.
The Remote Access Connection Manager is a service that handles the details of establishing the connection to the remote server. This service also provides the client with status information during the connection operation. The Remote Access Connection Manager starts automatically when an application loads the RASAPI32.DLL
Which RRAS component is affected?
While RRAS can be considered a class of technologies, this update specifically addresses vulnerabilities identified with the Remote Access Connection Manager Service also known as RASMAN. For additional information on RRAS and RRAS related technologies please see the following MSDN article on Routing and Remote Access.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
Who could exploit the vulnerability?
On Windows 2000 Service Pack 4 and Windows XP Service Pack 1, any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability. In order to exploit the vulnerability on Windows XP Service Pack 2 and Windows Server 2003, an attacker must have valid login credentials to a target system.
How could an attacker exploit the vulnerability?
An attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component either locally or remotely.
What systems are primarily at risk from the vulnerability?
Microsoft Windows 2000, Windows XP and Windows Server 2003 are primarily at risk from this vulnerability. Systems that use Internet Connection Sharing or applications that call RASAPI32.dll are at risk as they cause the Remote Access Connection Manager to load automatically.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.
Could the vulnerability be exploited over the Internet?
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 validating the way that Routing and Remote Access handles RPC related requests.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.
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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 uninstallation. |
| /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- kb911280-v2-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 KB911280.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-kb911280-v2-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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
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%\$NTUninstallKB911280$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Rasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 11:22 | 169,984 | RTMGDR |
| Rasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 11:18 | 170,496 | RTMQFE |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 11:33 | 181,760 | SP1GDR |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 11:51 | 181,760 | SP1QFE |
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Rasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 12:08 | 462,336 | IA-64 | RTMGDR |
| Wrasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 12:08 | 169,984 | x86 | RTMGDR\WOW |
| Rasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 12:10 | 462,848 | IA-64 | RTMQFE |
| Wrasmans.dll | 5.2.3790.549 | 22-Jun-2006 | 12:10 | 170,496 | x86 | RTMQFE\WOW |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:11 | 512,512 | IA-64 | SP1GDR |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:11 | 181,760 | x86 | SP1GDR\WOW |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:09 | 512,512 | IA-64 | SP1QFE |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:09 | 181,760 | x86 | SP1QFE\WOW |
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:10 | 287,744 | x64 | SP1GDR |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:10 | 181,760 | x86 | SP1GDR\WOW |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:08 | 287,744 | x64 | SP1QFE |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:08 | 181,760 | x86 | SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about 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.
The security update installer uses Arpidfix.exe to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB911280\Filelist
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\KB911280\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 security update into the Windows installation source files.
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 uninstallation. |
| /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- kb911280-v2-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 KB911280.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- kb911280-v2-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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911280$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Ipsec.sys | 5.1.2600.1842 | 13-May-2006 | 10:13 | 74,368 | SP1QFE |
| Ipsecsnp.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 334,848 | SP1QFE |
| Ipsecsvc.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 159,744 | SP1QFE |
| Ipsmsnap.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 364,544 | SP1QFE |
| Oakley.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 257,536 | SP1QFE |
| Polstore.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 98,304 | SP1QFE |
| Rasmans.dll | 5.1.2600.1861 | 22-Jun-2006 | 10:59 | 169,984 | SP1QFE |
| Winipsec.dll | 5.1.2600.1842 | 14-May-2006 | 09:13 | 29,184 | SP1QFE |
| Gptext.dll | 5.1.2600.1581 | 25-Aug-2004 | 22:07 | 183,808 | SP1QFE\IP |
| Rasmans.dll | 5.1.2600.2936 | 22-Jun-2006 | 10:47 | 181,248 | SP2GDR |
| Rasmans.dll | 5.1.2600.2936 | 22-Jun-2006 | 10:36 | 180,736 | SP2QFE |
Windows XP Professional x64:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:10 | 287,744 | x64 | SP1GDR |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:10 | 181,760 | x86 | SP1GDR\WOW |
| Rasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:08 | 287,744 | x64 | SP1QFE |
| Wrasmans.dll | 5.2.3790.2731 | 22-Jun-2006 | 12:08 | 181,760 | x86 | SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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\KB911280\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB911820\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 security update into the Windows installation source files.
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).
The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.
Installation Information
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 uninstallation. |
| /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- kb911280-v2-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 KB911280.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- kb911280-v2-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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911280$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows 2000 Service Pack 4 and Small Business Server 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Ipsec.sys | 5.0.2195.6738 | 22-Apr-2003 | 06:49 | 80,848 |
| Ipsecmon.exe | 5.0.2195.6738 | 22-Apr-2003 | 06:49 | 29,456 |
| Netdiag.exe | 5.0.2195.6738 | 22-Apr-2003 | 06:51 | 390,928 |
| Oakley.dll | 5.0.2195.6738 | 02-May-2003 | 13:09 | 417,552 |
| Polagent.dll | 5.0.2195.6738 | 02-May-2003 | 13:09 | 96,528 |
| Polstore.dll | 5.0.2195.6738 | 02-May-2003 | 13:09 | 137,488 |
| Rasmans.dll | 5.0.2195.7099 | 22-Jun-2006 | 00:47 | 161,040 |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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\KB911280\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 security update into the Windows installation source files.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Peter Winter-Smith of NGS Software for reporting the RASMAN Registry Corruption Vulnerability (CVE-2006-2371).
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available at the Microsoft Update Web site.
Support:
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Security Resources:
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Windows Server Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Microsoft Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.
Windows Server Update Services:
By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.
For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
Disclaimer:
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions:
V1.0 (June 13, 2006): Bulletin published
V1.1 (June 19, 2006): FAQ and Vulnerability Details sections updated to provide clarification on affected RASMAN component. Caveats section updated to include known issues.
V1.2 (June 21, 2006): Bulletin updated to provide additional differentiation between RRAS, RAS, and RASMAN components.
V2.0 (June 27, 2006): Microsoft updated this bulletin and the associated security updates to address the issues affecting customers identified in Microsoft Knowledge Base Article 911280.
Built at 2014-04-18T13:49:36Z-07:00