__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Vulnerability in Microsoft Agent Could Allow Spoofing (890046) [Microsoft Security Bulletin MS05-032] June 15, 2005 12:00 GMT Number P-229 [REVISED 10 AUG 2005] [REVISED 11 May 2007] ______________________________________________________________________________ PROBLEM: There is a spoofing vulnerability that exists in the affected products and that could enable an attacker to spoof trusted Internet content. PLATFORM: • Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 • Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) • Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) • Microsoft Windows XP Professional x64 Edition • Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems • Microsoft Windows Server 2003 x64 Edition • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems. DAMAGE: This vulnerability could enable an attacker to spoof trusted Internet content. SOLUTION: Upgrade to the appropriate version. ______________________________________________________________________________ VULNERABILITY The risk is LOW. An attacker would first have to persuade a ASSESSMENT: user to visit the attacker's site to attempt to exploit this vulnerability. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/p-229.shtml ORIGINAL BULLETIN: Microsoft Security Bulletin MS05-032 http://www.microsoft.com/technet/security/Bulletin/MS05-032.mspx CVE/CAN: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name= CAN-2005-1214 ______________________________________________________________________________ REVISION HISTORY: 08/10/2005 - CIAC has revised P-229 because Microsoft updated their bulletin MS05-032 to advise customers that a revised version of the security update is available for x64-based systems, Microsoft Windows Server 2003 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems. 05/11/2007 - revised P-229 because Microsoft updated their bulletin MS05-032 is not replaced by MS06-068. See "Why am I receiving this update" in the Frequently Asked Questions (FAQ) in this bulletin's Security Update Section for more information. Customers should install this update from this bulletin (MS05-032) as well as bulletin (MS06-068). [***** Start Microsoft Security Bulletin MS05-032 *****] Microsoft Security Bulletin MS05-032 Vulnerability in Microsoft Agent Could Allow Spoofing (890046) Issued: June 14, 2005 | Updated: May 8, 2007 Version: 2.1 Summary Who should read this document: Customers who use Microsoft Windows Impact of Vulnerability: Spoofing Maximum Severity Rating: Moderate Recommendation: Customers should consider applying the security update. Security Update Replacement: None Caveats: None Tested Software and Security Update Download Locations: Affected Software: • Microsoft Windows 2000 Service Pack 3 and 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 64-Bit Edition Service Pack 1 (Itanium) – Download the update • Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) – 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 • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems. The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site. Top of section General Information Executive Summary Executive Summary: This update resolves a newly-discovered, privately-reported vulnerability. This vulnerability could enable an attacker to spoof trusted Internet content. The vulnerability is documented in the “Vulnerability Details” section of this bulletin. We recommend that customers consider applying the security update. Severity Ratings and Vulnerability Identifiers: Vulnerability Identifiers Impact of Vulnerability Windows 98, 98 SE, ME Windows 2000 Windows XP Service Pack 1 Windows XP Service Pack 2 Windows Server 2003 Windows Server 2003 Service Pack 1 Microsoft Agent Vulnerability - CAN-2005-1214 Spoofing Not Critical Moderate Moderate Moderate Low Low This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them. Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows: • The Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating. • The Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating. • The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating. • The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating. • The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. • The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. Vulnerability Details Microsoft Agent Vulnerability - CAN-2005-1214: This is a spoofing vulnerability that exists in the affected products and that could enable an attacker to spoof trusted Internet content. Users could believe that they are accessing trusted Internet content. However, they are accessing malicious Internet content such as a malicious Web site. An attacker would first have to persuade a user to visit the attacker’s site to attempt to exploit this vulnerability. Mitigating Factors for Microsoft Agent Vulnerability - CAN-2005-1214: • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious 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 Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions. • 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. • By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability. See the FAQ section of this vulnerability for more information about Internet Explorer Enhanced Security Configuration. Top of section Workarounds for Microsoft Agent Vulnerability - CAN-2005-1214: Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section. • Set Internet and Local intranet security zone settings to “High” to disable running ActiveX controls in these zones. You can help protect against this vulnerability by changing your settings for the Internet security zone to disable 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: 1. On the Internet Explorer Tools menu, click Internet Options. 2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon. 3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High. 4. Repeat step 1 through step 3 and select the Local intranet security zone. 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 high security setting. See the “Restrict Web sites to only your trusted Web sites” workaround for information about how you can add sites to the Trusted sites zone. Alternatively, you can change your settings to prompt before running ActiveX controls only. To do this, follow these steps: 1. In Internet Explorer, click Internet Options on the Tools menu. 2. Click the Security tab. 3. Click Internet, and then click Custom Level. 4. Under Settings, in the Scripting section, under Active Scripting, click Prompt, and then click OK. 5. Click Local intranet, and then click Custom Level. 6. Under Settings, in the ActiveX Controls and Plug-ins section, under Run ActiveX controls and plugs-ins, click Prompt. 7. Click OK two times to return to Internet Explorer. Impact of Workaround: There are side effects to disabling running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX controls to provide additional functionality. Disabling running ActiveX controls is a global setting that affects all Internet and intranet sites. If you do not want to disable ActiveX controls for all sites, use the "Restrict Web sites to only your trusted Web sites" workaround. • Restrict Web sites to only your trusted Web sites. After you set Internet Explorer to disable ActiveX controls in the Internet zone and in the Local intranet zone, you can add sites that you trust to Internet Explorer's Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone. To do this, follow these steps: 1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. 2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites. 3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box. 4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add. 5. Repeat these steps for each site that you want to add to the zone. 6. Click OK two times to accept the changes and return to Internet Explorer. Add any sites that you trust not to take malicious action on your computer. One in particular that you may want to add is "*.windowsupdate.microsoft.com" (without the quotation marks). This is the site that will host the update, and it requires an ActiveX control to install the update. Top of section FAQ for Microsoft Agent Vulnerability - CAN-2005-1214: What is the scope of the vulnerability? This is a spoofing vulnerability. This vulnerability could enable an attacker to spoof trusted Internet content. Users could believe that they are accessing trusted Internet content. However, they are accessing malicious Internet content such as a malicious Web site. An attacker would first have to persuade a user to visit the attacker’s site to attempt to exploit this vulnerability. What causes the vulnerability? Security prompts can be disguised by a Microsoft Agent character. A user could be convinced to unintentionally allow the installation of malicious software. 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 spoof trusted Internet content. Users could believe they are accessing trusted Internet content when in reality they are accessing malicious Internet content. Security prompts, as well as other types of Internet content, could be spoofed if an attacker is successfully able to exploit this vulnerability. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of the affected system. Who could exploit the vulnerability? Any anonymous attacker who could display a specially crafted Web page to a user could attempt to exploit this 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 malicious 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. It could also be possible to display malicious Web content using banner advertisements or other ways to deliver Web content to affected systems. What systems are primarily at risk from the vulnerability? Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this. 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 mitigates this vulnerability. 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 of an administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and on the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following: • The security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads. • Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone. • Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running. • Multimedia content is disabled. This setting prevents music, animations, and video clips from running. What does the update do? The update removes the vulnerability by modifying the way that Microsoft Agent references characters. Users will now be prompted before a Microsoft Agent character is installed. 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. Top of section Top of section Top of section 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. Inclusion in Future Service Packs: The update for this issue will be included in future Service Pack or Update Rollup. Installation Information This security update supports the following setup switches. Supported Security Update Installation 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /overwriteoem Overwrites OEM files without prompting /nobackup Does not backup files needed for uninstall /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files /integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. /extract[:path] Extracts files without starting the Setup program /ER Enables extended error reporting /verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Deployment Information To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003: Windowsserver2003-kb890046-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 KB890046.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-kb890046-x86-enu /norestart For information about how to deploy this security update by using Software Update Services, visit the Software Update Services 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 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%\$NTUninstallKB890046$\Spuninst folder. Supported Spuninst.exe 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files File Information The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1: File Name Version Date Time Size Folder Agentdpv.dll 2.0.0.3423 11-May-2005 20:11 54,272 RTMGDR Ws03res.dll 5.2.3790.332 13-May-2005 23:54 2,560 RTMGDR Agentdpv.dll 2.0.0.3423 11-May-2005 20:06 54,272 RTMQFE Ws03res.dll 5.2.3790.332 13-May-2005 23:57 59,392 RTMQFE Agentdpv.dll 5.2.3790.1241 11-May-2005 20:22 58,880 SP1GDR W03a2409.dll 5.2.3790.2446 18-May-2005 00:43 3,072 SP1GDR Agentdpv.dll 5.2.3790.1241 11-May-2005 20:20 58,880 SP1QFE W03a2409.dll 5.2.3790.2446 18-May-2005 00:46 3,072 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 Agentdpv.dll 2.0.0.3423 14-Jul-2005 16:38 176,128 IA-64 RTMGDR Ws03res.dll 5.2.3790.370 14-Jul-2005 16:38 2,048 IA-64 RTMGDR Wagentdpv.dll 2.0.0.3423 14-Jul-2005 16:38 54,272 x86 RTMGDR\WOW Wws03res.dll 5.2.3790.370 14-Jul-2005 16:38 2,560 x86 RTMGDR\WOW Agentdpv.dll 2.0.0.3423 14-Jul-2005 16:38 176,128 IA-64 RTMQFE Ws03res.dll 5.2.3790.370 14-Jul-2005 16:38 58,880 IA-64 RTMQFE Wagentdpv.dll 2.0.0.3423 14-Jul-2005 16:38 54,272 x86 RTMQFE\WOW Wws03res.dll 5.2.3790.370 14-Jul-2005 16:38 59,392 x86 RTMQFE\WOW Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 201,728 IA-64 SP1GDR W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 2,048 IA-64 SP1GDR Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 58,880 x86 SP1GDR\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,072 x86 SP1GDR\WOW Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:38 201,728 IA-64 SP1QFE W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:38 2,048 IA-64 SP1QFE Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:38 58,880 x86 SP1QFE\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:38 3,072 x86 SP1QFE\WOW Arpidfix.exe 5.2.3790.2487 14-Jul-2005 16:38 74,752 IA-64 Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition: File Name Version Date Time Size CPU Folder Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 96,768 x64 SP1GDR W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,584 x64 SP1GDR Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 58,880 x86 SP1GDR\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,072 x86 SP1GDR\WOW Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 96,768 x64 SP1QFE W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,584 x64 SP1QFE Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 58,880 x86 SP1QFE\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,072 x86 SP1QFE\WOW Arpidfix.exe 5.2.3790.2487 14-Jul-2005 16:37 43,008 x64 Note When you install this security update on Windows Server 2003, 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 an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system. 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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. • File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. • Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry keys. Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB890046\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 890046 security update into the Windows installation source files. Top of section 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. Supported Security Update Installation 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /overwriteoem Overwrites OEM files without prompting /nobackup Does not backup files needed for uninstall /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files /integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. /extract[:path] Extracts files without starting the Setup program /ER Enables extended error reporting /verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Deployment Information To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP: Windowsxp-kb890046-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 KB890046.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-kb890046-x86-enu /norestart For information about how to deploy this security update by using Software Update Services, visit the Software Update Services 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%\$NTUninstallKB890046$\Spuninst folder. Supported Spuninst.exe 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files File Information The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005: File Name Version Date Time Size Folder Agentdpv.dll 2.0.0.3423 22-Apr-2005 05:20 51,712 SP1QFE Xpsp3res.dll 5.1.2600.1688 17-May-2005 00:43 7,168 SP1QFE Agentdpv.dll 2.0.0.3423 22-Apr-2005 05:06 57,344 SP2GDR Xpsp3res.dll 5.1.2600.2678 17-May-2005 00:25 15,360 SP2GDR Agentdpv.dll 2.0.0.3423 22-Apr-2005 05:18 57,344 SP2QFE Xpsp3res.dll 5.1.2600.2678 17-May-2005 00:26 17,920 SP2QFE Windows XP 64-Bit Edition Service Pack 1 (Itanium): File Name Version Date Time Size CPU Folder Agentdpv.dll 2.0.0.3423 09-May-2005 20:43 190,976 IA-64 SP1QFE Xpsp3res.dll 5.1.2600.1688 17-May-2005 00:58 6,656 IA-64 SP1QFE Wagentdpv.dll 2.0.0.3423 09-May-2005 20:43 51,712 x86 SP1QFE\WOW Wxpsp3res.dll 5.1.2600.1688 17-May-2005 00:43 7,168 x86 SP1QFE\WOW Windows XP 64-Bit Edition Version 2003 (Itanium): File Name Version Date Time Size CPU Folder Agentdpv.dll 2.0.0.3423 18-May-2005 20:05 176,128 IA-64 RTMGDR Ws03res.dll 5.2.3790.332 18-May-2005 20:05 2,048 IA-64 RTMGDR Wagentdpv.dll 2.0.0.3423 18-May-2005 20:05 54,272 x86 RTMGDR\WOW Wws03res.dll 5.2.3790.332 18-May-2005 20:05 2,560 x86 RTMGDR\WOW Agentdpv.dll 2.0.0.3423 18-May-2005 20:05 176,128 IA-64 RTMQFE Ws03res.dll 5.2.3790.332 18-May-2005 20:05 58,880 IA-64 RTMQFE Wagentdpv.dll 2.0.0.3423 18-May-2005 20:05 54,272 x86 RTMQFE\WOW Wws03res.dll 5.2.3790.332 18-May-2005 20:05 59,392 x86 RTMQFE\WOW Agentdpv.dll 5.2.3790.1241 18-May-2005 20:05 201,728 IA-64 SP1GDR W03a2409.dll 5.2.3790.2446 18-May-2005 20:05 2,048 IA-64 SP1GDR Wagentdpv.dll 5.2.3790.1241 18-May-2005 20:05 58,880 x86 SP1GDR\WOW Ww03a2409.dll 5.2.3790.2446 18-May-2005 20:05 3,072 x86 SP1GDR\WOW Agentdpv.dll 5.2.3790.1241 18-May-2005 20:05 201,728 IA-64 SP1QFE W03a2409.dll 5.2.3790.2446 18-May-2005 20:05 2,048 IA-64 SP1QFE Wagentdpv.dll 5.2.3790.1241 18-May-2005 20:05 58,880 x86 SP1QFE\WOW Ww03a2409.dll 5.2.3790.2446 18-May-2005 20:05 3,072 x86 SP1QFE\WOW Windows XP Professional x64: File Name Version Date Time Size CPU Folder Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 96,768 x64 SP1GDR W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,584 x64 SP1GDR Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 58,880 x86 SP1GDR\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,072 x86 SP1GDR\WOW Agentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 96,768 x64 SP1QFE W03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,584 x64 SP1QFE Wagentdpv.dll 5.2.3790.1241 14-Jul-2005 16:37 58,880 x86 SP1QFE\WOW Ww03a2409.dll 5.2.3790.2487 14-Jul-2005 16:37 3,072 x86 SP1QFE\WOW Arpidfix.exe 5.2.3790.2487 14-Jul-2005 16:37 43,008 x64 Notes The Windows XP security update is packaged as a dual-mode package. Dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2). For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848. 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 an affected file, one of the following conditions occurs, depending on your operating system: • Windows XP SP2 The installer copies the SP2QFE files to your system. • Windows XP 64-Bit Edition Version 2003 (Itanium) The installer copies the RTMQFE files to your system. If you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system: • Windows XP SP2 The installer copies the SP2GDR files to your system. • Windows XP 64-Bit Edition Version 2003 (Itanium) The installer copies the RTMGDR files to your system. 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. Note For Windows XP 64-Bit Edition Version 2003 (Itanium), this security update is the same as the Windows Server 2003 for Itanium-based Systems security update. For Microsoft Windows XP Professional x64 Edition, this security update is the same as the Microsoft Windows Server 2003 x64 Edition security update. Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. • File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. • Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry keys. For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB890046\Filelist For Windows XP 64-Bit Edition Version 2003 (Itanium): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB890046\Filelist For Windows XP Professional x64 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB890046\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 890046 security update into the Windows installation source files. Top of section Windows 2000 (all versions) Prerequisites For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4). The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site. For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910. Inclusion in Future Service Packs: The update for this issue may be included in a future Update Rollup. Installation Information This security update supports the following setup switches. Supported Security Update Installation 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /overwriteoem Overwrites OEM files without prompting /nobackup Does not backup files needed for uninstall /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files /integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. /extract[:path] Extracts files without starting the Setup program /ER Enables extended error reporting /verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. Deployment Information To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4: Windows2000-kb890046-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 KB890046.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 3 and Windows 2000 Service Pack 4: Windows2000-kb890046-x86-enu /norestart For more information about how to deploy this security update with Software Update Services, visit the Software Update Services 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%\$NTUninstallKB890046$\Spuninst folder. Supported Spuninst.exe 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 force other applications to close at shutdown without saving open files first. /warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. /promptrestart Display a dialog box prompting the local user to allow a restart Special Options /forceappsclose Forces other programs to close when the computer shuts down /log:path Allows the redirection of installation log files File Information The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, and Small Business Server 2000: File Name Version Date Time Size Agentdpv.dll 2.0.0.3423 18-May-2005 06:54 53,008 Sp3res.dll 5.0.2195.7040 21-Apr-2005 10:07 6,309,376 Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. • File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. • Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB890046\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 890046 security update into the Windows installation source files. Top of section Top of section Acknowledgments Microsoft thanks the following for working with us to help protect customers: • Michael Krax for reporting the Microsoft Agent Vulnerability (CAN-2005-1214). Obtaining Other Security Updates: Updates for other security issues are available at the following locations: • Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." • Updates for consumer platforms are available at the Windows Update Web site. Support: • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site. Security Resources: • The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. • Microsoft Software Update Services • Microsoft Baseline Security Analyzer (MBSA) • Windows 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 this security update by using Software Update Services, visit the Software 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 Analyze, 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 14, 2005): Bulletin published • V1.1 (June 29, 2005): Bulletin “Security Update Information” section revised with updated details for the Windows XP x64 Professional Edition registry key verification information. • V2.0 (August 9, 2005): Microsoft updated this bulletin to advise customers that a revised version of the security update is available for x64-based systems, Microsoft Windows Server 2003 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems. • V2.1 (May 8, 2007): MS05-032 is not replaced by MS06-068. See “Why am I receiving this update” in the Frequently Asked Question (FAQ) in this bulletin’s Security Update Section for more information. Customers should install this update from this bulletin (MS05-032) as well as bulletin (MS06-068).. [***** End Microsoft Security Bulletin MS05-032 *****] _______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Microsoft for the information contained in this bulletin. _______________________________________________________________________________ CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 925-422-8193 (7x24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@ciac.org Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://www.ciac.org/ Anonymous FTP: ftp.ciac.org PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) P-219: tcpdump Security Update P-220: Squid Security Update P-221: Vulnerability in Server Message Block Could Allow Remote Code Execution (896422) P-222: Internet Explorer Cumulative Security Update P-223: Vulnerability in HTML Help Could Allow Remote Code Execution (896358) P-224: Windows Web Client Service Vulnerability P-225: Outlook Web Access for Exchange Server 5.5 Vulnerability P-226: Outlook Express Cumulative Update P-227: Step-by-Step Interactive Training Vulnerability P-228: ISA Server 2000 Cumulative Update