Overview
Adobe Reader and Acrobat fail to properly handle U3D data, which could allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.
Description
Adobe Reader supports two primary formats for 3D content in PDF documents: U3D and PRC. U3D support is accomplished via the Right Hemisphere 3DIF Import filter, which is provided by the 3difr.x3d file. This U3D parser contains a vulnerability that can result in arbitrary code execution. The following versions of Adobe Acrobat and Reader versions are affected:
|
Impact
By convincing a user to view a specially crafted PDF document with embedded U3D content, an attacker may be able to execute arbitrary code. This vulnerability is being exploited in the wild, and exploit code is publicly available. |
Solution
We are currently unaware of a practical solution to this problem.Adobe has stated in security advisory APSA11-04: We are in the process of finalizing a fix for the issue and expect to make available an update for Adobe Reader and Acrobat 9.x for Windows no later than the week of December 12, 2011. We are planning to address this issue in Adobe Reader and Acrobat X and earlier versions for Macintosh as part of the next quarterly update scheduled for January 10, 2012. An update to address this issue in Adobe Reader 9.x for UNIX is planned for January 10, 2012. |
According to Adobe security advisory APSA11-04 the following mitigations can be used to address this vulnerability: Adobe Reader X Protected Mode and Adobe Acrobat X Protected View would prevent an exploit of this kind from executing. To verify Protected View for Acrobat X is enabled, go to: Edit >Preferences > Security (Enhanced) and ensure "Files from potentially unsafe locations" or "All files" with "Enable Enhanced Security" are checked. To verify Protected Mode for Adobe Reader X is enabled, go to: Edit >Preferences >General and verify that "Enable Protected Mode at startup" is checked. Use the Microsoft Enhanced Mitigation Experience Toolkit The Microsoft Enhanced Mitigation Experience Toolkit (EMET) can be used to help prevent exploitation of this and other vulnerabilities. Enable DEP in Microsoft Windows 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. Note that when relying on DEP for exploit mitigation, it is important to use a system that supports Address Space Layout Randomization (ASLR) as well. ASLR is not supported by Windows XP or Windows Server 2003 or earlier. ASLR was introduced with Microsoft Windows Vista and Windows Server 2008. Please see the Microsoft SRD blog entry: On the effectiveness of DEP and ASLR for more details. Disable JavaScript in Adobe Reader and Acrobat Disabling JavaScript helps to reduce attack surface and mitigates some exploitation techniques. If this workaround is applied to updated versions of Adobe Reader and Acrobat, it may protect against future vulnerabilities. To disable JavaScript in Adobe Reader:
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:
[HKEY_CLASSES_ROOT\AcroExch.Document.7] "EditFlags"=hex:00,00,00,00 Preventing PDF documents from opening inside a web browser reduces 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 being opened in a web browser with Adobe Reader:
|
Vendor Information
CVSS Metrics
| Group | Score | Vector |
|---|---|---|
| Base | 0 | AV:--/AC:--/Au:--/C:--/I:--/A:-- |
| Temporal | 0 | E:ND/RL:ND/RC:ND |
| Environmental | 0 | CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND |
References
- https://www.adobe.com/support/security/advisories/apsa11-04.html
- http://blogs.adobe.com/asset/2011/12/background-on-cve-2011-2462.html
- http://www.microsoft.com/download/en/details.aspx?id=1677
- http://blogs.technet.com/b/srd/archive/2009/06/05/understanding-dep-as-a-mitigation-technology-part-1.aspx
- http://blogs.technet.com/b/srd/archive/2009/06/12/understanding-dep-as-a-mitigation-technology-part-2.aspx
- http://blogs.technet.com/b/srd/archive/2010/12/08/on-the-effectiveness-of-dep-and-aslr.aspx
- http://technet.microsoft.com/en-us/security/advisory/2639658
Acknowledgements
This vulnerability was reported by Adobe, who in turn credit the Lockheed Martin CIRT and DSIE for reporting the issue.
This document was written by Michael Orlando and Will Dormann.
Other Information
| CVE IDs: | CVE-2011-2462 |
| Severity Metric: | 52.51 |
| Date Public: | 2011-12-06 |
| Date First Published: | 2011-12-08 |
| Date Last Updated: | 2011-12-08 22:06 UTC |
| Document Revision: | 36 |