Privacy policy. This security update resolves one privately reported and one publicly disclosed vulnerability. The privately reported vulnerability could allow remote code execution if a user viewed a specially crafted Web page using Internet Explorer.
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 publicly disclosed vulnerability could allow information disclosure if a user viewed a specially crafted Web page using Internet Explorer.
The security update is also rated Important for Internet Explorer 5. For more information, see the subsection, Affected and Non-Affected Software , in this section. The security update addresses these vulnerabilities by modifying the way that Internet Explorer handles calls to HTML objects and validates data.
Microsoft recommends that customers apply the update immediately. The software listed here have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Why was this bulletin revised on June 11, ? This bulletin was revised to communicate that the file information in the associated Microsoft Knowledge Base Article has been updated. Where are the file information details?
The file information details can be found in the Microsoft Knowledge Base Article I am using an older release of the software discussed in this security bulletin.
What should I do? The affected software listed in this bulletin have been tested to determine which releases are affected. These hotfixes may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains these hotfixes. For more information about how to install the hotfixes that are included in security update , click the following article number to view the article in the Microsoft Knowledge Base:.
For more information about how to determine whether your existing Internet Explorer files are from the hotfix or from the GDR environment, click the following article number to view the article in the Microsoft Knowledge Base:. The English United States version of this security update has the file attributes or later file attributes that are listed in the following table.
Internet Explorer 6 stops responding after you install security update on a computer that is running Windows XP Service Pack 2. On a Windows XP SP2-based computer that has certain cumulative security updates for Internet Explorer installed, Internet Explorer 6 may stop responding when you try to visit a Web site. The exception handler may not catch an exception in Internet Explorer 7 or in Internet Explorer 6 when you view a Web page that throws an exception from a function that is called through the expando property.
You have to enter credentials multiple times when you use a Office application that takes advantage of multiple network stacks. If no existing Internet Explorer files are from the hotfix environment, security update installs the GDR files.
Hotfixes are intended to correct only the problems that are described in the Microsoft Knowledge Base articles that are associated with the hotfixes. Apply hotfixes only to systems that are experiencing these specific problems. These hotfixes may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains these hotfixes.
With Excel Viewer, you can open, view, and print Excel workbooks, even if you don't have Excel installed. You can also copy data from Excel Viewer to another program. However, you cannot edit data, save a workbook, or create a new workbook.
I am using an older release of the software discussed in this security bulletin. What should I do? The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle. It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities.
For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services. Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office.
For contact information, visit Microsoft Worldwide Information , select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see Microsoft Knowledge Base Article Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image.
For more information on how to change the source for a client computer from an updated administrative installation point to an Office original baseline source or Service Pack 2 SP2 , see Microsoft Knowledge Base Article Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, Distributing Office Product Upgrades. For supported versions of the Microsoft Office system, see Create a network installation point for the Office system.
Updates often write to the same files and registry settings required for your applications to run.
0コメント