Adobe Security Bulletin

Release date: January 5, 2017

Last updated: March 30, 2017

Vulnerability identifier: APSB17-01

Priority: 2

CVE numbers: CVE-2017-2939, CVE-2017-2940, CVE-2017-2941, CVE-2017-2942, CVE-2017-2943, CVE-2017-2944, CVE-2017-2945, CVE-2017-2946, CVE-2017-2947, CVE-2017-2948, CVE-2017-2949, CVE-2017-2950, CVE-2017-2951, CVE-2017-2952, CVE-2017-2953, CVE-2017-2954, CVE-2017-2955, CVE-2017-2956, CVE-2017-2957, CVE-2017-2958, CVE-2017-2959, CVE-2017-2960, CVE-2017-2961, CVE-2017-2962, CVE-2017-2963, CVE-2017-2964, CVE-2017-2965, CVE-2017-2966, CVE-2017-2967, CVE-2017-2970, CVE-2017-2971, CVE-2017-2972, CVE-2017-3009, CVE-2017-3010

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 questions regarding Acrobat DC, please visit the Acrobat DC FAQ page. For questions regarding 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 a type confusion vulnerability that could lead to code execution (CVE-2017-2962).
• These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-2017-2950, CVE-2017-2951, CVE-2017-2955, CVE-2017-2956, CVE-2017-2957, CVE-2017-2958, CVE-2017-2961).
• These updates resolve heap buffer overflow vulnerabilities that could lead to code execution (CVE-2017-2942, CVE-2017-2945, CVE-2017-2946, CVE-2017-2949, CVE-2017-2959, CVE-2017-2966, CVE-2017-2970, CVE-2017-2971, CVE-2017-2972).
• These updates resolve buffer overflow vulnerabilities that could lead to code execution (CVE-2017-2948, CVE-2017-2952).
• These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2017-2939, CVE-2017-2940, CVE-2017-2941, CVE-2017-2943, CVE-2017-2944, CVE-2017-2953, CVE-2017-2954, CVE-2017-2960, CVE-2017-2963, CVE-2017-2964, CVE-2017-2965, CVE-2017-2967, CVE-2017-3010).
• These updates resolve a security bypass vulnerability (CVE-2017-2947).
• These updates resolve a buffer overflow vulnerability that could lead to information disclosure (CVE-2017-3009).

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:

• Jaanus Kääp of Clarified Security and Anonymous working with Trend Micro's Zero Day Initiative (CVE-2017-2939)
• kelvinwang of Tencent PC Manager (CVE-2017-2955, CVE-2017-2956, CVE-2017-2957, CVE-2017-2958)
• Steven Seeley of Source Incite working with Trend Micro's Zero Day Initiative and Kushal Arvind Shah of Fortinet's FortiGuard Labs (CVE-2017-2946)
• Sebastian Apelt (siberas) working with Trend Micro's Zero Day Initiative (CVE-2017-2961, CVE-2017-2967)
• Ke Liu of Tencent's Xuanwu LAB (CVE-2017-2940, CVE-2017-2942, CVE-2017-2943, CVE-2017-2944, CVE-2017-2945, CVE-2017-2952, CVE-2017-2953, CVE-2017-2954, CVE-2017-2972)
• kdot working with Trend Micro's Zero Day Initiative (CVE-2017-2941, CVE-2017-3009)
• Nicolas Grgoire (Agarri) working with Trend Micro's Zero Day Initiative (CVE-2017-2962)
• Nicolas Grégoire - Agarri working with iDefense Vulnerability Contributor Program (CVE-2017-2948)
• Anonymous working with Trend Micro's Zero Day Initiative (CVE-2017-2951, CVE-2017-2970)
• Anonymous working with Trend Micro's Zero Day Initiative and Anonymous working with iDefense (CVE-2017-2950)
  
• Ke Liu of Tencent's Xuanwu LAB working with Trend Micro's Zero Day Initiative and riusksk (泉哥) of Tencent Security Platform Department (CVE-2017-2959)
  
• Ke Liu of Tencent's Xuanwu LAB working with Trend Micro's Zero Day Initiative (CVE-2017-2960, CVE-2017-2963, CVE-2017-2964, CVE-2017-2965, CVE-2017-2966)
• Wei Lei and Liu Yang of Nanyang Technological University, Anonymous working with Trend Micro's Zero Day Initiative, and Nicolas Grégoire - Agarri working with iDefense Vulnerability Contributor Program (CVE-2017-2949)
• Alex Inführ of Cure53.de (CVE-2017-2947)
• Aleksandar Nikolic of Cisco Talos (CVE-2017-2971)
  
• Kushal Arvind Shah and Peixue Li of Fortinet's FortiGuard Labs (CVE-2017-3010)

January 20, 2017: Added references to CVE-2017-2970, CVE-2017-2971, and CVE-2017-2972, which were inadvertently omitted from the bulletin.

February 16, 2017: Updated acknowledgement to CVE-2017-2939, CVE-2017-2946, CVE-2017-2949, CVE-2017-2950 and CVE-2017-2959, which were inadvertently omitted from the bulletin.

March 30, 2017: Updated acknowledgement to CVE-2017-3009 and CVE-2017-3010, which were inadvertently omitted from the bulletin.