Microsoft Security Advisory 973472
Vulnerability in Microsoft Office Web Components Control Could Allow Remote Code Execution
Published: July 13, 2009 | Updated: August 11, 2009
Microsoft has completed the investigation of a privately reported vulnerability in Microsoft Office Web Components. We have issued MS09-043 to address this issue. For more information about this issue, including download links for an available security update, please review MS09-043. The vulnerability addressed is the Office Web Components HTML Script Vulnerability - CVE-2009-1136.
- You can provide feedback by completing the form by visiting the following Web site.
- Customers in the United States and Canada can receive technical support from Security Support. For more information about available support options, see the Microsoft Help and Support Web site.
- International customers can receive support from their local Microsoft subsidiaries. For more information about how to contact Microsoft for international support issues, visit the International Support Web site.
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
The information provided in this advisory 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.
- V1.0 (July 13, 2009): Advisory published.
- V1.1 (July 15, 2009): Updated the impact description of the workaround, "Prevent Office Web Components Library from running in Internet Explorer."
- V1.2 (July 23, 2009): Added additional workarounds.
- V2.0 (August 11, 2009): Advisory updated to reflect publication of security bulletin.
Built at 2014-04-18T13:49:36Z-07:00