Intrusion Prevention

MS.IE.Mouse.Event.Handler.Uninitialized.Memory.Corruption

Description

This indicates an attack attempt against a memory-corruption vulnerability in Microsoft Internet Explorer.
The vulnerability is caused by an error when the vulnerable software handles an HTML document with a malicious mouse event handler. It may allow remote attackers to execute arbitrary code by sending a crafted web page.

Affected Products

Internet Explorer 6 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4
Internet Explorer 6
Internet Explorer 6 for Windows XP Service Pack 2 and Windows XP Service Pack 3
Internet Explorer 6 for Windows XP Professional x64 Edition Service Pack 2
Internet Explorer 6 for Windows Server 2003 Service Pack 2
Internet Explorer 6 for Windows Server 2003 x64 Edition Service Pack 2
Internet Explorer 6 for Windows Server 2003 with SP2 for Itanium-based Systems
Internet Explorer 7
Internet Explorer 7 for Windows XP Service Pack 2 and Windows XP Service Pack 3
Internet Explorer 7 for Windows XP Professional x64 Edition Service Pack 2
Internet Explorer 7 for Windows Server 2003 Service Pack 2
Internet Explorer 7 for Windows Server 2003 x64 Edition Service Pack 2
Internet Explorer 7 for Windows Server 2003 with SP2 for Itanium-based Systems
Internet Explorer 7 in Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2
Internet Explorer 7 in Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2
Internet Explorer 7 in Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
Internet Explorer 7 in Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
Internet Explorer 7 in Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2

Impact

System Compromise: Remote attackers can gain control of vulnerable systems.

Recommended Actions

Refer to the vendor's web site for the suggested workaround:
http://www.microsoft.com/technet/security/Bulletin/ms10-018.mspx

CVE References

CVE-2010-0267