Adobe Security Bulletin

Release date: July 14, 2015

Vulnerability identifier: APSB15-15

Priority: See table below

CVE numbers: CVE-2014-0566, CVE-2014-8450, CVE-2015-3095, CVE-2015-4435, CVE-2015-4438, CVE-2015-4441, CVE-2015-4443, CVE-2015-4444, CVE-2015-4445, CVE-2015-4446, CVE-2015-4447, CVE-2015-4448, CVE-2015-4449, CVE-2015-4450, CVE-2015-4451, CVE-2015-4452, CVE-2015-5085, CVE-2015-5086, CVE-2015-5087, CVE-2015-5088, CVE-2015-5089, CVE-2015-5090, CVE-2015-5091, CVE-2015-5092, CVE-2015-5093, CVE-2015-5094, CVE-2015-5095, CVE-2015-5096, CVE-2015-5097, CVE-2015-5098, CVE-2015-5099, CVE-2015-5100, CVE-2015-5101, CVE-2015-5102, CVE-2015-5103, CVE-2015-5104, CVE-2015-5105, CVE-2015-5106, CVE-2015-5107, CVE-2015-5108, CVE-2015-5109, CVE-2015-5110, CVE-2015-5111, CVE-2015-5113, CVE-2015-5114, CVE-2015-5115

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 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. 

• These updates resolve a buffer overflow vulnerability that could lead to code execution (CVE-2015-5093).  
• These updates resolve heap buffer overflow vulnerabilities that could lead to code execution (CVE-2015-5096, CVE-2015-5098, CVE-2015-5105).  
• These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2015-5087, CVE-2015-5094, CVE-2015-5100, CVE-2015-5102, CVE-2015-5103, CVE-2015-5104, CVE-2015-3095, CVE-2015-5115, CVE-2014-0566). 
• These updates resolve an information leak vulnerability (CVE-2015-5107).  
• These updates resolve security bypass vulnerabilities that could lead to information disclosure (CVE-2015-4449, CVE-2015-4450, CVE-2015-5088, CVE-2015-5089, CVE-2015-5092, CVE-2014-8450).  
• These updates resolve a stack overflow vulnerability that could lead to code execution (CVE-2015-5110). 
• These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-2015-4448, CVE-2015-5095, CVE-2015-5099, CVE-2015-5101, CVE-2015-5111, CVE-2015-5113, CVE-2015-5114). 
• These updates resolve validation bypass issues that could be exploited to perform privilege escalation from low to medium integrity level (CVE-2015-4446, CVE-2015-5090, CVE-2015-5106). 
• These updates resolve a validation bypass issue that could be exploited to cause a denial-of-service condition on the affected system (CVE-2015-5091).  
• These updates resolve integer overflow vulnerabilities that could lead to code execution (CVE-2015-5097, CVE-2015-5108, CVE-2015-5109).  
• These updates resolve various methods to bypass restrictions on JavaScript API execution (CVE-2015-4435, CVE-2015-4438, CVE-2015-4441, CVE-2015-4445, CVE-2015-4447, CVE-2015-4451, CVE-2015-4452, CVE-2015-5085, CVE-2015-5086).  
• These updates resolve null-pointer dereference issues that could lead to a denial-of-service condition (CVE-2015-4443, CVE-2015-4444). 

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: 

• AbdulAziz Hariri and Jasiel Spelman of HP Zero Day Initiative (CVE-2015-5085, CVE-2015-5086, CVE-2015-5090, CVE-2015-5091) 
• AbdulAziz Hariri of HP Zero Day Initiative (CVE-2015-4438, CVE-2015-4447, CVE-2015-4452, CVE-2015-5093, CVE-2015-5094, CVE-2015-5095, CVE-2015-5101, CVE-2015-5102, CVE-2015-5103, CVE-2015-5104, CVE-2015-5113, CVE-2015-5114, CVE-2015-5115) 
• Alex Inführ of Cure53.de (CVE-2015-4449, CVE-2015-4450, CVE-2015-5088, CVE-2015-5089, CVE-2014-8450)  
• bilou working with VeriSign iDefense Labs (CVE-2015-4448, CVE-2015-5099) 
• Brian Gorenc of HP Zero Day Initiative (CVE-2015-5100, CVE-2015-5111) 
• Security Research Team at MWR Labs (@mwrlabs) (CVE-2015-4451) 
• James Forshaw of Google Project Zero (CVE-2015-4446) 
• Jihui Lu of KeenTeam (CVE-2015-5087) 
• JinCheng Liu of the Alibaba Security Research Team (CVE-2015-5096, CVE-2015-5097, CVE-2015-5098, CVE-2015-5105) 
• Keen Team working with HP's Zero Day Initiative (CVE-2015-5108) 
• kernelsmith working with HP's Zero Day Initiative (CVE-2015-4435, CVE-2015-4441) 
• Mateusz Jurczyk of Google Project Zero (CVE-2015-3095) 
• Matt Molinyawe of HP Zero Day Initiative (CVE-2015-4445) 
• Mauro Gentile of Minded Security (CVE-2015-5092) 
• Nicolas Joly working with HP's Zero Day Initiative (CVE-2015-5106, CVE-2015-5107, CVE-2015-5109, CVE-2015-5110) 
• Wei Lei and Wu Hongjun of Nanyang Technological University (CVE-2014-0566) 
• Wu Ha of the Alibaba Security Research Team (CVE-2015-4443, CVE-2015-4444)