Vulnerability Note VU#812969
Adobe Flash memory corruption vulnerability
Adobe Flash contains an memory corruption vulnerability that can allow a remote, unauthenticated attacker to execute arbitrary code.
Adobe Flash versions 10.1.102.64 and earlier contain a vulnerability that can result in memory corruption, which can allow arbitrary code execution. Please see Adobe Security Bulletin APSB11-02 and Adobe Security Bulletin APSB11-03.
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.102.64 and earlier versions for Windows, Macintosh, Linux, and Solaris.
Apply an update
Disable Flash in your web browser
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.
Vendor Information (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Adobe||Affected||31 Jan 2011||10 Feb 2011|
|Affected||-||10 Feb 2011|
CVSS Metrics (Learn More)
This vulerability was reported by Will Dormann of the CERT/CC.
This document was written by Will Dormann.
- CVE IDs: CVE-2011-0560 CVE-2011-0561
- Date Public: 08 Feb 2011
- Date First Published: 10 Feb 2011
- Date Last Updated: 28 Mar 2012
- Severity Metric: 12.76
- Document Revision: 15
If you have feedback, comments, or additional information about this vulnerability, please send us email.