Security updates available for Adobe Flash Player

Release date: July 12, 2016

Last updated: October 3, 2016

Vulnerability identifier: APSB16-25

Priority: See table below

CVE number: CVE-2016-4172, CVE-2016-4173, CVE-2016-4174, CVE-2016-4175, CVE-2016-4176, CVE-2016-4177, CVE-2016-4178, CVE-2016-4179, CVE-2016-4180, CVE-2016-4181, CVE-2016-4182, CVE-2016-4183, CVE-2016-4184, CVE-2016-4185, CVE-2016-4186, CVE-2016-4187, CVE-2016-4188, CVE-2016-4189, CVE-2016-4190, CVE-2016-4217, CVE-2016-4218, CVE-2016-4219, CVE-2016-4220, CVE-2016-4221, CVE-2016-4222, CVE-2016-4223, CVE-2016-4224, CVE-2016-4225, CVE-2016-4226, CVE-2016-4227, CVE-2016-4228, CVE-2016-4229, CVE-2016-4230, CVE-2016-4231, CVE-2016-4232, CVE-2016-4233, CVE-2016-4234, CVE-2016-4235, CVE-2016-4236, CVE-2016-4237, CVE-2016-4238, CVE-2016-4239, CVE-2016-4240, CVE-2016-4241, CVE-2016-4242, CVE-2016-4243, CVE-2016-4244, CVE-2016-4245, CVE-2016-4246, CVE-2016-4247, CVE-2016-4248, CVE-2016-4249, CVE-2016-7020

Platform: Windows, Macintosh, Linux and ChromeOS

Summary

Adobe has released security updates for Adobe Flash Player for Windows, Macintosh, Linux and ChromeOS.  These updates address critical vulnerabilities that could potentially allow an attacker to take control of the affected system.  

Affected Versions

Product Affected Versions Platform
Adobe Flash Player Desktop Runtime 22.0.0.192 and earlier
Windows and Macintosh
Adobe Flash Player Extended Support Release 18.0.0.360 and earlier Windows and Macintosh
Adobe Flash Player for Google Chrome 22.0.0.192 and earlier Windows, Macintosh, Linux and ChromeOS
Adobe Flash Player for Microsoft Edge and Internet Explorer 11 22.0.0.192 and earlier Windows 10 and 8.1
Adobe Flash Player for Linux 11.2.202.626 and earlier Linux
  • To verify the version of Adobe Flash Player installed on your system, access the About Flash Player page, or right-click on content running in Flash Player and select "About Adobe (or Macromedia) Flash Player" from the menu. If you use multiple browsers, perform the check for each browser you have installed on your system.  

Solution

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

Product Updated Versions Platform Priority rating Availability
Adobe Flash Player Desktop Runtime
22.0.0.209 Windows and Macintosh
1

Flash Player Download Center

Flash Player Distribution

Adobe Flash Player Extended Support Release 18.0.0.366 Windows and Macintosh
1 Extended Support
Adobe Flash Player for Google Chrome 22.0.0.209 Windows, Macintosh, Linux and ChromeOS   1 Google Chrome Releases
Adobe Flash Player for Microsoft Edge and Internet Explorer 11 22.0.0.209 Windows 10 and 8.1 1 Microsoft Security Advisory
Adobe Flash Player for Linux 11.2.202.632 Linux 3 Flash Player Download Center
  • Adobe recommends users of the  Adobe Flash Player Desktop Runtime for Windows and Macintosh update to 22.0.0.209 via the update mechanism within the product when prompted [1], or by visiting the Adobe Flash Player Download Center.
  • Adobe recommends users of the Adobe Flash Player Extended Support Release should update to version 18.0.0.366 by visiting http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html.
  • Adobe recommends users of Adobe Flash Player for Linux update to Adobe Flash Player 11.2.202.632 by visiting the Adobe Flash Player Download Center.
  • Adobe Flash Player installed with Google Chrome will be automatically updated to the latest Google Chrome version, which will include Adobe Flash Player 22.0.0.209 for Windows, Macintosh, Linux and Chrome OS.
  • Adobe Flash Player installed with Microsoft Edge and Internet Explorer for Windows 10 and 8.1 will be automatically updated to the latest version, which will include Adobe Flash Player 22.0.0.209. 
  • Please visit the Flash Player Help page for assistance in installing Flash Player.

[1] Users of Flash Player 11.2.x or later for Windows, or Flash Player 11.3.x or later for Macintosh, who have selected the option to 'Allow Adobe to install updates' will receive the update automatically. Users who do not have the 'Allow Adobe to install updates' option enabled can install the update via the update mechanism within the product when prompted.

Vulnerability Details

  • These updates resolve a race condition vulnerability that could lead to information disclosure (CVE-2016-4247).
  • These updates resolve type confusion vulnerabilities that could lead to code execution (CVE-2016-4223, CVE-2016-4224, CVE-2016-4225).
  • These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-2016-4173, CVE-2016-4174, CVE-2016-4222, CVE-2016-4226, CVE-2016-4227, CVE-2016-4228, CVE-2016-4229, CVE-2016-4230, CVE-2016-4231, CVE-2016-4248, CVE-2016-7020).
  • These updates resolve a heap buffer overflow vulnerability that could lead to code execution (CVE-2016-4249).
  • These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2016-4172, CVE-2016-4175, CVE-2016-4179, CVE-2016-4180, CVE-2016-4181, CVE-2016-4182, CVE-2016-4183, CVE-2016-4184, CVE-2016-4185, CVE-2016-4186, CVE-2016-4187, CVE-2016-4188, CVE-2016-4189, CVE-2016-4190, CVE-2016-4217, CVE-2016-4218, CVE-2016-4219, CVE-2016-4220, CVE-2016-4221, CVE-2016-4233, CVE-2016-4234, CVE-2016-4235, CVE-2016-4236, CVE-2016-4237, CVE-2016-4238, CVE-2016-4239, CVE-2016-4240, CVE-2016-4241, CVE-2016-4242, CVE-2016-4243, CVE-2016-4244, CVE-2016-4245, CVE-2016-4246).
  • These updates resolve a memory leak vulnerability (CVE-2016-4232).
  • These updates resolve stack corruption vulnerabilities that could lead to code execution (CVE-2016-4176, CVE-2016-4177).
  • These updates resolve a security bypass vulnerability that could lead to information disclosure (CVE-2016-4178)

Acknowledgments

  • Yuki Chen of Qihoo 360 Vulcan Team working with the Chromium Vulnerability Rewards Program (CVE-2016-4249)
  • Nicolas Joly of Microsoft Vulnerability Research (CVE-2016-4173)
  • Wen Guanxing from Pangu LAB (CVE-2016-4188, CVE-2016-4248)
  • Jaehun Jeong(@n3sk) of WINS WSEC Analysis Team working with Trend Micro's Zero Day Initiative (CVE-2016-4222)
  • Kai Kang (a.k.a 4B5F5F4B) working with Trend Micro's Zero Day Initiative (CVE-2016-4174)
  • willJ of Tencent PC Manager (CVE-2016-4172)
  • Natalie Silvanovich of Google Project Zero (CVE-2016-4226, CVE-2016-4227, CVE-2016-4228, CVE-2016-4229, CVE-2016-4230, CVE-2016-4231, CVE-2016-4232)
  • Garandou Sara working with Trend Micro's Zero Day Initiative (CVE-2016-4223)
  • Sébastien Morin of COSIG (CVE-2016-4179)
  • Sébastien Morin of COSIG, Francis Provencher of COSIG and b0nd@garage4hackers working with Trend Micro's Zero Day Initiative (CVE-2016-4175)
  • Kurutsu Karen working with Trend Micro's Zero Day Initiative (CVE-2016-4225)
  • Soroush Dalili and Matthew Evans from NCC Group (CVE-2016-4178)
  • Yuki Chen of Qihoo 360 Vulcan Team (CVE-2016-4180, CVE-2016-4181, CVE-2016-4183, CVE-2016-4184, CVE-2016-4185, CVE-2016-4186, CVE-2016-4187, CVE-2016-4233, CVE-2016-4234, CVE-2016-4235, CVE-2016-4236, CVE-2016-4239, CVE-2016-4240, CVE-2016-4241, CVE-2016-4242, CVE-2016-4243, CVE-2016-4244, CVE-2016-4245, CVE-2016-4246)
  • Yuki Chen of Qihoo 360 Vulcan Team, Wen Guanxing from Pangu LAB and Tao Yan of Palo Alto Networks (CVE-2016-4182)
  • Yuki Chek of Qihoo 360 Vulcan Team and Tao Yan of Palo Alto Networks (CVE-2016-4237, CVE-2016-4238) 
  • Junfeng Yang and Genwei Jiang of FireEye and Yuki Chen of Qihoo 360 Vulcan Team (CVE-2016-4185)
  • Ohara Rinne working with Trend Micro's Zero Day Initiative (CVE-2016-4224)
  • Francis Provencher of COSIG (CVE-2016-4176, CVE-2016-4177)
  • Jie Zeng of Tencent Zhanlu Lab (CVE-2016-4189, CVE-2016-4190, CVE-2016-4217, CVE-2016-4218, CVE-2016-4219, CVE-2016-4220, CVE-2016-4221)
  • JieZeng of Tencent Zhanlu Lab, working with the Chromium Vulnerability Rewards Program (CVE-2016-7020)
  • Stefan Kanthak (CVE-2016-4247)

Revisions

August 22, 2016: Added credit for CVE-2016-4237, CVE-2016-4238 and CVE-2016-4182 to Tao Yan of Palo Alto Networks.   

August 26, 2016: Updated credit for CVE-2016-4175. 

October 3, 2016: Updated credit for CVE-2016-7020.

June 19, 2017: Updated credit for CVE-2016-4175.