Research > Zero-Day Tracker > 20101104
Adobe Reader printSeps() Heap Corruption
Date Disclosed:
11/4/2010
Date Patched:
Partially Patched 11.16.2010 (Reader/Acrobat 9.x for Windows and Mac)
Vendor:
Adobe
Affected Software:
Adobe Reader 8.x for UNIX.
Description:
Adobe Reader contain a heap corruption vulnerability that is caused by an undocumented API call, printSeps(). Calling this function, which is found in escript.api, could lead to an application crash or more potently, execution of arbitrary code in the context of the current user.
Severity:
High
Code Execution:
Yes
Impact:
Remote Code Execution in current user's context
This client-side issue may be exploited by an attacker by tricking a user to open a malicious PDF document with Adobe Reader. Once the user has opened the file, the attacker may remotely execute arbitrary code in the context of the current user. If the user is an administrator, the attacker could install malicious software and further compromise the system.
Mitigation:
Disable JavaScript in the Preferences menu in Adobe Reader.
Protection:
- eEye's Retina® Network Security Scanner scans devices to detect for this vulnerability.
- Retina Audit 13715 - Adobe Reader PrintSeps() Heap Corruption (Zero-Day) - UNIX/Linux
Links:
Status:
- 11.4.2010 - Public Information Released
- 11.16.2010 - Partially Patched (Reader 9.x for Windows and Mac) 12.1.2011 - Partially Patched (Unix 9.x)
- 12.1.2011 - Partially Patched (Unix 9.x)
- 2.8.2011 - Partially Patched (Reader 8.x for Windows and Mac)
Copyright ©1998-2011 eEye Digital Security
Permission is hereby granted for the redistribution of this alert electronically. It is not to be edited in any way without express consent of eEye. If you wish to reprint the whole or any part of this alert in any other medium excluding electronic medium, please email alert@eEye.com for permission.
Disclaimer
The information within this paper may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are no warranties, implied or express, with regard to this information. In no event shall the author be liable for any direct or indirect damages whatsoever arising out of or in connection with the use or spread of this information. Any use of this information is at the user's own risk.