Adobe Flash 10.1.85.3 contains a vulnerability that can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.
Adobe Flash 10.1.85.3 and earlier versions as well as 10.2.161.23 and earlier 10.2 preview versions contain a vulnerability that can result in memory corruption, which can allow arbitrary code execution. Any application that supports Flash or provides its own runtime may be vulnerable. This vulnerability is being exploited in the wild.
By convincing a user to view a specially crafted HTML document (e.g., a web page or an HTML email message or attachment), PDF file, Microsoft Office document, or any other document that supports embedded SWF content, an attacker may be able to execute arbitrary code.
Apply an update
This issue is addressed in Adobe Flash 10.1.102.64. More details are available in Adobe Security Bulletin APSB10-26. Adobe Reader and Acrobat 9.4.1 address this issue. More details are available in APSB10-28. For other affected products, please see Adobe Security Bulletin APSA10-05 and consider the following workarounds:
Prevent Internet Explorer from automatically opening PDF documents
The installer for Adobe Reader and Acrobat configures Internet Explorer to automatically open PDF files without any user interaction. This behavior can be reverted to the safer option of prompting the user by importing the following as a .REG file:
Windows Registry Editor Version 5.00
Disable the displaying of PDF documents in the web browser
Preventing PDF documents from opening inside a web browser reduces the attack surface. If this workaround is applied to updated versions of Adobe Reader and Acrobat, it may protect against future vulnerabilities.
To prevent PDF documents from automatically opening in a web browser with Adobe Reader:
Consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be treated as a complete workaround, but it can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts "Understanding DEP as a mitigation technology" part 1 and part 2. DEP should be used in conjunction with the application of patches or other mitigations described in this document.
This document was written by Will Dormann.
|Date First Published:||2010-10-28|
|Date Last Updated:||2010-11-17 17:39 UTC|