• Microsoft Windows XP Service Pack 3
• Microsoft Windows XP Professional x64 Edition Service Pack 2
• Microsoft Windows Server 2003 Service Pack 2
• Microsoft Windows Server 2003 x64 Edition Service Pack 2
• Microsoft Windows Server 2003 SP2 (Itanium)
• Microsoft Windows Vista Service Pack 1
• Microsoft Windows Vista Service Pack 2
• Microsoft Windows Vista x64 Edition Service Pack 1
• Microsoft Windows Vista x64 Edition Service Pack 2
• Microsoft Windows Server 2008 (32-bit)
• Microsoft Windows Server 2008 (32-bit) Service Pack 2
• Microsoft Windows Server 2008 (64x)
• Microsoft Windows Server 2008 (64x) Service Pack 2
• Microsoft Windows Server 2008 (Itanium)
• Microsoft Windows Server 2008 (Itanium) Service Pack 2
• Microsoft Windows 7 (32-bit)
• Microsoft Windows 7 (64x)
• Microsoft Windows Server 2008 R2 (64x)
• Microsoft Windows Server 2008 R2 (Itanium)

• Microsoft Internet Explorer 6
• Microsoft Internet Explorer 7
• Microsoft Internet Explorer 8

A remote code execution vulnerabilities has been reported in Microsoft Internet Explorer ,Successful exploitation of these vulnerabilities allow disclosure of sensitive information and execution of arbitrary code.

The vulnerability exists due to improper security restrictions on data stored within the Internet Explorer AutoComplete feature. The vulnerability could allow web pages to access stored data by simulating user actions, possibly resulting in the disclosure of sensitive information.

An unauthenticated, remote attacker could exploit this vulnerability by convincing a user to view a malicious website. When viewed, the website could allow the attacker to capture data stored within the users browser, possibly resulting in the disclosure of user-credentials, e-mail addresses, or other recently-submitted data.

The vulnerability is due to improper handling of strings in HTML content.  The affected applications do not sufficiently sanitize strings that are received in requests from the toStaticHTML API.  As a result, unfiltered content may be displayed in the users browser.

An unauthenticated, remote attacker could exploit the vulnerability by convincing a user to view a URL that is designed to submit malicious values to a targeted website.  When followed, the URL could cause the website to return malicious, unfiltered values to the users browser.  The returned values may be improperly handled and included in the website that is rendered in the users browser.  The attacker could take advantage of this behavior to conduct cross-site scripting attacks.

The vulnerability exists because the toStaticHTML application programming interface (API) fails to perform proper string sanitization.

An unauthenticated, remote attacker could exploit the vulnerability by convincing a user to view a URL that is designed to submit malicious data to a website that calls the Internet Explorer toStaticHTML API to filter user-supplied input.  When viewed, the URL could send malicious data to the website, which may return the data unfiltered to the users browser.  As a result, the attacker could execute arbitrary script or HTML code in the users browser.

The vulnerability is due to the improper processing of special characters in CSS documents.

An unauthenticated, remote attacker could exploit this vulnerability by convincing a user to view a malicious website.  When viewed, the website could allow the attacker to access stored information from other security domains.  Exploitation could lead to the disclosure of sensitive browser-based information, such as temporary files, recently submitted data, or user credentials.

The vulnerability is due to improper handling of unspecified HTML content. An unauthenticated, remote attacker could exploit this vulnerability by convincing a user to view a malicious website. When viewed, the website could cause Internet Explorer to access a previously removed memory object, which could result in memory corruption. The attacker could leverage the memory corruption to execute arbitrary code with the privileges of the user.

An unauthorized attacker could gain access to information on an affected system. Personally identifying information contained within an anchor element, which the user has previously deleted, may appear during HTML content editing operations.

The vulnerability is due to improper memory operations performed by the CAttrArray::PrivateFind() function in the mshtml.dll library of the affected software.

An unauthenticated, remote attacker could exploit the vulnerability by convincing a user to open a website containing a malicious style sheet property. The processing of the property could cause the vulnerable library to unexpectedly free a memory object. Later access of the memory object could trigger memory corruption. The attacker could exploit the memory corruption to execute arbitrary code with the privileges of the user.

The vulnerability is due to errors when instantiating a HtmlDlgHelper Class Object in the mshtmled.dll module in Internet Explorer.

An unauthenticated, remote attacker could exploit the vulnerability by convincing a user to visit a malicious website containing an embedded Microsoft Office document. Processing the malicious website could cause Internet Explorer to call the destructor class CHtmlDlgHelper Class Object, resulting in an access of unintialized memory and triggering memory corruption. The attacker could take advantage of the memory corruption to execute arbitrary code with the privileges of the user.

The vulnerability exists due to improper determination of script domain origins within Internet Explorer.  Scripts running within Internet Explorer may be able to access data from other security zones.  As a result, confidential information from other security zones may be exposed, possibly resulting in information disclosure.

An unauthenticated, remote attacker could exploit this vulnerability by convincing a user to view a malicious website.  When viewed, scripts running on the site could retrieve data from other security zones on the targeted system, resulting in the disclosure of sensitive information.

The vulnerability exists when Internet Explorer processes web content. The application performs improper memory operations on uninitialized or previously removed memory objects.

An unauthenticated, remote attacker could exploit this vulnerability by convincing a user to view a malicious website. Processing the website could cause Internet Explorer to perform an invalid memory operation, which could corrupt memory. The attacker could leverage the memory corruption to execute arbitrary code with the privileges of the user.

• Read e-mails in plain text
• Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones
• Add sites that you trust to the Internet Explorer Trusted sites zone
• Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone
• Use Microsoft Office File Block policy to block the opening of HTML documents from unknown or untrusted sources and locations