Security Bulletin
Microsoft Security Bulletin MS06-068 - Critical
Vulnerability in Microsoft Agent Could Allow Remote Code Execution (920213)
Published: November 14, 2006 | Updated: October 10, 2007
Version: 1.2
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: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows 2000 Service Pack 4 — Download the update
- 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:
- Windows Vista
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 a newly discovered, privately reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
We recommend that customers apply the update immediately
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 2000 Service Pack 4 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
|---|---|---|---|---|---|
| Microsoft Agent Memory Corruption Vulnerability - CVE-2006-3445 | Remote Code Execution | Critical | Critical | 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 security updates for 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 Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
- The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
- The 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 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
What updates does this release replace?
Customers who did not receive updates prior to MS06-068 may not have received MS05-032 and therefore should apply MS05-032 immediately. However, customers who have installed both MS06-068 and MS07-045 will have the security update provided by MS05-032 and do not need to install MS05-032 separately. Customers who have installed MS06-068 only, or who have not installed both MS06-068 and MS07-045, should install MS05-032.
Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1 has reached the end of its support life cycle. 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.
Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do?
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support 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.
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 support 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.
| Product | MBSA 1.2.1 | MBSA 2.0 |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
| 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 programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
For more detailed information, see Microsoft Knowledge Base Article 910723.
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.
| Product | SMS 2.0 | SMS 2003 |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
| 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 programs 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.
For more detailed information, see Microsoft Knowledge Base Article 910723.
Vulnerability Details
Microsoft Agent Memory Corruption Vulnerability - CVE-2006-3445:
There is a remote code execution vulnerability in the way that Microsoft Agent handles specially crafted .ACF files. An attacker could exploit the vulnerability by constructing a specially crafted Web page that could potentially allow remote code execution if a user viewed the Web page. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
Mitigating Factors for Microsoft Agent Memory Corruption Vulnerability - CVE-2006-3445:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
- The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario. By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally Outlook 2000 opens HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed.
- By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.
Workarounds for Microsoft Agent Memory Corruption Vulnerability - CVE-2006-3445:
Temporarily prevent the Microsoft Agent ActiveX control from running in Internet Explorer
You can help prevent attempts to instantiate this ActiveX control in Internet Explorer by setting the kill bit for the control in the registry.Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the Registry Editor at your own risk.
For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
To set the kill bit for a CLSID with a value of {CLSID}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{D45FD31B-5C6E-11D1-9EC1-00C04FD7081F}]
"Compatibility Flags"=dword:00000400
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{F5BE8BD2-7DE6-11D0-91FE-00C04FD701A5}]
"Compatibility Flags"=dword:00000400
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4BAC124B-78C8-11D1-B9A8-00C04FD97575}]
"Compatibility Flags"=dword:00000400
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{D45FD31D-5C6E-11D1-9EC1-00C04FD7081F}]
"Compatibility Flags"=dword:00000400
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{D45FD31E-5C6E-11D1-9EC1-00C04FD7081F}]
"Compatibility Flags"=dword:00000400
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
What is Group Policy Object Editor?
Core Group Policy tools and settings
Note You must restart Internet Explorer for your changes to take effect.
Impact of Workaround: Web sites that use the Microsoft Agent ActiveX Control may no longer display or function correctly.
Configure Internet Explorer to prompt before running ActiveX Controls or disable ActiveX Controls in the Internet and Local intranet security zone
You can help protect against this vulnerability by changing your Internet Explorer settings to prompt before running ActiveX controls. To do this, follow these steps:- In Internet Explorer, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Internet, and then click Custom Level.
- Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.
Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones
You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.To raise the browsing security level in Microsoft Internet Explorer, follow these steps:
- On the Internet Explorer Tools menu, click Internet Options.
- In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
- Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.
Note If no slider is visible, click Default Level, and then move the slider to High.
Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.
FAQ for Microsoft Agent Memory Corruption Vulnerability - CVE-2006-3445:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
When Microsoft Agent handles specially crafted .ACF files it may corrupt system memory in such a way that an attacker could execute arbitrary code.
What is Microsoft Agent?
Microsoft Agent is a software technology that enables an enriched form of user interaction that can make using and learning to use a computer easier and more natural. For more information, see the Microsoft Agent Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Who could exploit the vulnerability?
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and visits a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
I am running Internet Explorer 7. Does this mitigate this vulnerability?
Yes. Customers who are running Internet Explorer 7 with default settings, are not at risk until the MS Agent ActiveX control has been activated through the ActiveX opt-in feature in the Internet Zone.
What is the ActiveX Opt-in feature in Internet Explorer 7?
Internet Explorer 7 includes an ActiveX opt-in feature, which means that nearly all pre-installed ActiveX controls are off by default. Users are prompted by the Information Bar before they can access a previously installed ActiveX Control that has not yet been used on the Internet. This enables a user to permit or deny access on a control-by-control basis. For more information about this and other new features see the Windows Internet Explorer 7 features page.
I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003 runs in a restricted mode. that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.
What is Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this threat by modifying numerous security-related settings, including Security and Advanced tab settings in Internet Options. Some of the key modifications include:
- Security level for the Internet zone is set to High. This setting disables scripts, ActiveX components, Microsoft virtual machine (Microsoft VM) HTML content, and file downloads.
- Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
- Install on Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
- Multimedia content is disabled. This setting prevents music, animations, and video clips from running.
For more information regarding Internet Explorer Enhanced Security Configuration, please consult the Managing Internet Explorer Enhanced Security Configuration guide, which can be found at the following Web site.
What does the update do?
The update removes the vulnerability by modifying the way that Microsoft Agent validates the length of a message before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
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 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-KB920213-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 KB920213.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-KB920213-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%\$NTUninstallKB920213$\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 |
|---|---|---|---|---|
| Agentdp2.dll | 2.0.0.3424 | 24-Aug-2006 | 08:07 | 41,744 |
| Agentdpv.dll | 2.0.0.3424 | 24-Aug-2006 | 08:07 | 53,008 |
| Agentsvr.exe | 2.0.0.3424 | 23-Aug-2006 | 16:48 | 242,448 |
| Sp3res.dll | 5.0.2195.7087 | 03-May-2006 | 06:57 | 6,401,024 |
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\KB920213\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.
Windows XP (all versions)
Prerequisites This security update requires Microsoft Windows XP Service Pack 2. 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-KB920213-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 KB920213.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-KB920213-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%\$NTUninstallKB920213$\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 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 |
|---|---|---|---|---|---|
| Agentdp2.dll | 2.0.0.3424 | 12-Oct-2006 | 14:02 | 42,496 | SP2GDR |
| Agentdpv.dll | 2.0.0.3424 | 12-Oct-2006 | 14:02 | 57,344 | SP2GDR |
| Agentsvr.exe | 2.0.0.3424 | 12-Oct-2006 | 11:09 | 256,512 | SP2GDR |
| Xpsp3res.dll | 5.1.2600.3016 | 16-Oct-2006 | 10:21 | 115,200 | SP2GDR |
| Agentdp2.dll | 2.0.0.3424 | 12-Oct-2006 | 13:54 | 42,496 | SP2QFE |
| Agentdpv.dll | 2.0.0.3424 | 12-Oct-2006 | 13:54 | 57,344 | SP2QFE |
| Agentsvr.exe | 2.0.0.3424 | 12-Oct-2006 | 11:54 | 256,512 | SP2QFE |
| Xpsp3res.dll | 5.1.2600.3016 | 16-Oct-2006 | 10:29 | 248,320 | SP2QFE |
Windows XP Professional x64:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 64,512 | x64 | SP1GDR |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 96,768 | x64 | SP1GDR |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 470,016 | x64 | SP1GDR |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:26 | 4,608 | x64 | SP1GDR |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 43,520 | x86 | SP1GDR\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 58,880 | x86 | SP1GDR\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 258,560 | x86 | SP1GDR\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:26 | 4,096 | x86 | SP1GDR\WOW |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 64,512 | x64 | SP1QFE |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 96,768 | x64 | SP1QFE |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 470,016 | x64 | SP1QFE |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 27,648 | x64 | SP1QFE |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 43,520 | x86 | SP1QFE\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 58,880 | x86 | SP1QFE\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 258,560 | x86 | SP1QFE\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 27,136 | 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.
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 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\KB920213\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB920213\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 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-KB920213-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 KB920213.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-KB920213-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.
This security update does not support HotPatching. For more information about HotPatching and how to deploy this security update as a HotPatch see Microsoft Knowledge Base Article 897341.
Note Not all security updates support HotPatching, and some security updates that support HotPatching might require that you restart the server after you install the security update. HotPatching is only supported if the files being replaced by the security update are General Distribution Release (GDR) files. For more information about this behavior, see Microsoft Knowledge Base Article 897341 and Microsoft Knowledge Base Article 824994.
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%\$NTUninstallKB920213$\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 |
|---|---|---|---|---|---|
| Agentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 22:26 | 40,448 | RTMGDR |
| Agentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 22:26 | 54,272 | RTMGDR |
| Agentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 11:52 | 239,104 | RTMGDR |
| Ws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 11:39 | 2,560 | RTMGDR |
| Agentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 22:28 | 40,448 | RTMQFE |
| Agentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 22:28 | 54,272 | RTMQFE |
| Agentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 11:52 | 239,104 | RTMQFE |
| Ws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 11:50 | 67,072 | RTMQFE |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 22:41 | 43,520 | SP1GDR |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:24 | 58,880 | SP1GDR |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 12:07 | 258,560 | SP1GDR |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 11:54 | 4,096 | SP1GDR |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 22:55 | 43,520 | SP1QFE |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 22:55 | 58,880 | SP1QFE |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 12:40 | 258,560 | SP1QFE |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 12:27 | 27,136 | 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 |
|---|---|---|---|---|---|---|
| Agentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 125,952 | IA-64 | RTMGDR |
| Agentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 176,128 | IA-64 | RTMGDR |
| Agentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 825,344 | IA-64 | RTMGDR |
| Ws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 23:22 | 2,048 | IA-64 | RTMGDR |
| Wagentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 40,448 | x86 | RTMGDR\WOW |
| Wagentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 54,272 | x86 | RTMGDR\WOW |
| Wagentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 239,104 | x86 | RTMGDR\WOW |
| Wws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 23:22 | 2,560 | x86 | RTMGDR\WOW |
| Agentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 125,952 | IA-64 | RTMQFE |
| Agentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 176,128 | IA-64 | RTMQFE |
| Agentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 825,344 | IA-64 | RTMQFE |
| Ws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 23:22 | 66,560 | IA-64 | RTMQFE |
| Wagentdp2.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 40,448 | x86 | RTMQFE\WOW |
| Wagentdpv.dll | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 54,272 | x86 | RTMQFE\WOW |
| Wagentsvr.exe | 2.0.0.3424 | 30-Aug-2006 | 23:22 | 239,104 | x86 | RTMQFE\WOW |
| Wws03res.dll | 5.2.3790.586 | 30-Aug-2006 | 23:22 | 67,072 | x86 | RTMQFE\WOW |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 141,312 | IA-64 | SP1GDR |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 201,728 | IA-64 | SP1GDR |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 913,408 | IA-64 | SP1GDR |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:25 | 3,072 | IA-64 | SP1GDR |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 43,520 | x86 | SP1GDR\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 58,880 | x86 | SP1GDR\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:25 | 258,560 | x86 | SP1GDR\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:25 | 4,096 | x86 | SP1GDR\WOW |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 141,312 | IA-64 | SP1QFE |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 201,728 | IA-64 | SP1QFE |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 913,408 | IA-64 | SP1QFE |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 26,112 | IA-64 | SP1QFE |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 43,520 | x86 | SP1QFE\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 58,880 | x86 | SP1QFE\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 258,560 | x86 | SP1QFE\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 27,136 | 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 |
|---|---|---|---|---|---|---|
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 64,512 | x64 | SP1GDR |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 96,768 | x64 | SP1GDR |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 470,016 | x64 | SP1GDR |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:26 | 4,608 | x64 | SP1GDR |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 43,520 | x86 | SP1GDR\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 58,880 | x86 | SP1GDR\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:26 | 258,560 | x86 | SP1GDR\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:26 | 4,096 | x86 | SP1GDR\WOW |
| Agentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 64,512 | x64 | SP1QFE |
| Agentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 96,768 | x64 | SP1QFE |
| Agentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 470,016 | x64 | SP1QFE |
| W03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 27,648 | x64 | SP1QFE |
| Wagentdp2.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 43,520 | x86 | SP1QFE\WOW |
| Wagentdpv.dll | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 58,880 | x86 | SP1QFE\WOW |
| Wagentsvr.exe | 5.2.3790.1242 | 30-Aug-2006 | 23:22 | 258,560 | x86 | SP1QFE\WOW |
| Ww03a2409.dll | 5.2.3790.2781 | 30-Aug-2006 | 23:22 | 27,136 | 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.
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, 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\KB920213\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.
Other Information
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.
- TechNet Update Management Center
- 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 Scan 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 (November 14, 2006): Bulletin published.
- V1.1 (May 8, 2007): The FAQ has been changed to show that Bulletin MS06-068 does not replace bulletin MS05-032. See “What updates does this release replace” in the Frequently Asked Questions (FAQ) in this bulletin’s Security Update section for more information. Customers should install the update from this bulletin (MS06-068) as well as the previous bulletin (MS05-032).
- V1.2: Clarified that MS05-032 is only replaced when both MS06-068 and MS07-045 are installed. For more information, see “What updates does this release replace?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update.
Built at 2014-04-18T13:49:36Z-07:00