Adobe Security Bulletin

Release date: April 6, 2017

Last updated: August 8, 2017

Vulnerability identifier: APSB17-11

Priority: 2

CVE numbers: CVE-2017-3011, CVE-2017-3012, CVE-2017-3013, CVE-2017-3014, CVE-2017-3015, CVE-
2017-3017, CVE-2017-3018, CVE-2017-3019, CVE-2017-3020, CVE-2017-3021, CVE-2017-3022, CVE-
2017-3023, CVE-2017-3024, CVE-2017-3025, CVE-2017-3026, CVE-2017-3027, CVE-2017-3028, CVE-
2017-3029, CVE-2017-3030, CVE-2017-3031, CVE-2017-3032, CVE-2017-3033, CVE-2017-3034, CVE-
2017-3035, CVE-2017-3036, CVE-2017-3037, CVE-2017-3038, CVE-2017-3039, CVE-2017-3040, CVE-
2017-3041, CVE-2017-3042, CVE-2017-3043, CVE-2017-3044, CVE-2017-3045, CVE-2017-3046, CVE-
2017-3047, CVE-2017-3048, CVE-2017-3049, CVE-2017-3050, CVE-2017-3051, CVE-2017-3052, CVE-
2017-3053, CVE-2017-3054, CVE-2017-3055, CVE-2017-3056, CVE-2017-3057, CVE-2017-3065

Platform: Windows and Macintosh

Adobe has released security updates for Adobe Acrobat and Reader for Windows and Macintosh. These updates address critical vulnerabilities that could potentially allow an attacker to take control of the affected system.

For more information on Acrobat DC, please visit the Acrobat DC FAQ page.

For more information on Acrobat Reader DC, please visit the Acrobat Reader DC FAQ page.

Adobe recommends users update their software installations to the latest versions by following the
instructions below.
The latest product versions are available to end users via one of the following methods:

• Users can update their product installations manually by choosing Help > Check for Updates.
• The products will update automatically, without requiring user intervention, when updates are
  detected.
• The full Acrobat Reader installer can be downloaded from the Acrobat Reader Download Center.
  

For IT administrators (managed environments):

• Download the enterprise installers from ftp://ftp.adobe.com/pub/adobe/, or refer to the specific release note version for links to installers.
• Install updates via your preferred methodology, such as AIP-GPO, bootstrapper, SCUP/SCCM
  (Windows), or on Macintosh, Apple Remote Desktop and SSH.
  

Adobe categorizes these updates with the following priority ratings and recommends users update their installation to the newest version:

• These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-
  2017-3014, CVE-2017-3026, CVE-2017-3027, CVE-2017-3035, CVE-2017-3047, CVE-2017-3057).
• These updates resolve heap buffer overflow vulnerabilities that could lead to code execution
  (CVE-2017-3042, CVE-2017-3048, CVE-2017-3049, CVE-2017-3055).
• These updates resolve memory corruption vulnerabilities that could lead to code execution
  (CVE-2017-3015, CVE-2017-3017, CVE-2017-3018, CVE-2017-3019, CVE-2017-3023, CVE-2017-
  3024, CVE-2017-3025, CVE-2017-3028, CVE-2017-3030, CVE-2017-3036, CVE-2017-3037, CVE-
  2017-3038, CVE-2017-3039, CVE-2017-3040, CVE-2017-3041, CVE-2017-3044, CVE-2017-3050,
  CVE-2017-3051, CVE-2017-3054, CVE-2017-3056, CVE-2017-3065).
• These updates resolve integer overflow vulnerabilities that could lead to code execution (CVE-
  2017-3011, CVE-2017-3034).
• These updates resolve memory corruption vulnerabilities that could lead to a memory address
  leak (CVE-2017-3020, CVE-2017-3021, CVE-2017-3022, CVE-2017-3029, CVE-2017-3031, CVE-
  2017-3032, CVE-2017-3033, CVE-2017-3043, CVE-2017-3045, CVE-2017-3046, CVE-2017-3052,
  CVE-2017-3053).
• These updates resolve vulnerabilities in the directory search path used to find resources that
  could lead to code execution (CVE-2017-3012, CVE-2017-3013).
  

Adobe would like to thank the following individuals and organizations for reporting the
relevant issues and for working with Adobe to help protect our customers:

• Nicolas Gregoire - Agarri working with Trend Micro's Zero Day Initiative (CVE-2017-3031)
• Weizhong Qian, Fuhao Li and Huinian Yang of ART&UESTC's Neklab (CVE-2017-3037)
• Anonymously reported via iDefense Vulnerability Contributor Program (VCP) (CVE-2017-3014,
  CVE-2017-3027)
• riusksk (CVE-2017-3039)
• riusksk working with Trend Micro's Zero Day Initiative (CVE-2017-3040)
  
• LiuBenjin of Qihoo360 CodeSafe Team working with Trend Micro's Zero Day Initiative (CVE-2017-
  3055)
• Nikolas Sotiriu (CVE-2017-3013)
• willj from Tencent PC Manager working with Trend Micro’s Zero Day Initiative (CVE-2017-3056, CVE-2017-3057)
• Toan Pham Van ( @__suto ) (CVE-2017-3041)
• AbdulAziz Hariri of Trend Micro's Zero Day Initiative and Steven Seeley (mr_me) of Offensive
  Security working with Trend Micro's Zero Day Initiative (CVE-2017-3042)
• AbdulAziz Hariri of Trend Micro's Zero Day Initiative (CVE-2017-3043)
• Ashfaq Ansari - Project Srishti via iDefense Vulnerability Contributor Program (VCP) (CVE-2017-
  3038)
• Steven Seeley (mr_me) of Offensive Security (CVE-2017-3026, CVE-2017-3054)
• kimyok of Tencent Security Platform Department (CVE-2017-3017, CVE-2017-3018, CVE-2017-3024, CVE-2017-3025, CVE-2017-3065)
• kdot working with Trend Micro's Zero Day Initiative (CVE-2017-3019)
• GRIMM (CVE-2017-3030)
• Steven Seeley (mr_me) of Offensive Security working with Trend Micro's Zero Day Initiative
  (CVE-2017-3047, CVE-2017-3049)
• Steven Seeley (mr_me) of Offensive Security working with Trend Micro's Zero Day Initiative and Ke Liu of Tencent's Xuanwu LAB (CVE-2017-3050)
  
• Ke Liu of Tencent's Xuanwu LAB (CVE-2017-3012, CVE-2017-3015)
• soiax working with Trend Micro's Zero Day Initiative (CVE-2017-3022)
• Sebastian Apelt (Siberas) working with Trend Micro's Zero Day Initiative (CVE-2017-3034, CVE-
  2017-3035)
• Ke Liu of Tencent's Xuanwu LAB working with Trend Micro's Zero Day Initiative (CVE-2017-3020,
  CVE-2017-3021, CVE-2017-3023, CVE-2017-3028, CVE-2017-3036, CVE-2017-3048, CVE-2017-
  3051, CVE-2017-3052, CVE-2017-3053)
• Jun Mao of Tencent PC Manager via GeekPwn (CVE-2017-3011)
• Giwan Go of STEALIEN working with Trend Micro's Zero Day Initiative (CVE-2017-3029, CVE-
  2017-3032, CVE-2017-3033, CVE-2017-3044, CVE-2017-3045, CVE-2017-3046)
  

April 27, 2017: Updated acknowledgement to CVE-2017-3050 which were inadvertently omitted from the bulletin.

May 11, 2017: Updated acknowledgement to CVE-2017-3040 which were inadvertently omitted from the bulletin.

August 8, 2017: Added a note below the vulnerability details section to clarify status of CVE-2017-3038.