Vulnerability Note VU#275289
Adobe Flash unspecified code execution vulnerability
Adobe Flash contains an unspecified vulnerability that can allow a remote, unauthenticated attacker to execute arbitrary code.
Note that separate instances of Flash are provided in a variety of Adobe products, including Adobe Reader and Acrobat. Updating Flash Player does not update the Flash runtime included in other products.
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. The vulnerability reportedly affects Flash Player 10.1.82.76 and earlier versions for Windows, Macintosh, Linux, and Solaris, Flash Player 10.1.92.10 for Android, and Adobe Reader and Acrobat 9.3.4 and earlier.
Apply an update
"/Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/Adobe3D.framework"
Adobe has provided a TechNote with utilities for uninstalling the Flash Player plug-in and ActiveX control on Windows and Mac OS X systems. Removing these components can mitigate the web browser attack vector for this vulnerability. Note that this will not remove the instances of Flash Player that are installed with Adobe Reader or other Adobe products.
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:
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.
Vendor Information (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Adobe||Affected||10 Sep 2010||21 Sep 2010|
|Affected||-||21 Sep 2010|
CVSS Metrics (Learn More)
The vendor credits Bo Qu of Palo Alto Networks.
This document was written by Will Dormann.
- CVE IDs: CVE-2010-2884
- Date Public: 13 Sep 2010
- Date First Published: 13 Sep 2010
- Date Last Updated: 21 Sep 2010
- Severity Metric: 31.59
- Document Revision: 14
If you have feedback, comments, or additional information about this vulnerability, please send us email.