First published: Thu Jun 16 2016(Updated: )
Unspecified vulnerability in Adobe Flash Player 21.0.0.242 and earlier, as used in the Adobe Flash libraries in Microsoft Internet Explorer 10 and 11 and Microsoft Edge, has unknown impact and attack vectors, a different vulnerability than other CVEs listed in MS16-083.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat enterprise Linux desktop | =5.0 | |
redhat enterprise Linux desktop | =6.0 | |
redhat enterprise Linux server | =5.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux workstation | =5.0 | |
redhat enterprise Linux workstation | =6.0 | |
Adobe Acrobat Reader | <=21.0.0.242 | |
Adobe Flash Player | <=21.0.0.242 | |
Apple iOS and macOS | ||
Chrome OS | ||
Linux Kernel | ||
Microsoft Windows | ||
Microsoft Windows 10 | ||
Microsoft Windows 8.1 | ||
Adobe Acrobat Reader | <=21.0.0.242 | |
Adobe Acrobat Reader | <=21.0.0.242 | |
Adobe Acrobat Reader | <=11.2.202.621 | |
Adobe Acrobat Reader | <=18.0.0.352 | |
openSUSE | =13.1 | |
openSUSE | =13.2 | |
SUSE Linux Enterprise Desktop with Beagle | =12 | |
SUSE Linux Enterprise Desktop with Beagle | =12-sp1 | |
SUSE Linux Enterprise Workstation Extension | =12 | |
SUSE Linux Enterprise Workstation Extension | =12-sp1 | |
Adobe Acrobat Reader | ||
Microsoft Windows 10 | =1511 | |
Microsoft Windows RT | ||
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2012 x64 | =r2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-4145 is currently unknown due to its unspecified nature.
To mitigate CVE-2016-4145, updating Adobe Flash Player to version 21.0.0.243 or later is recommended.
CVE-2016-4145 affects Adobe Flash Player 21.0.0.242 and earlier versions in several environments including Red Hat Enterprise Linux and various Windows browsers.
The impacts of CVE-2016-4145 are not fully defined due to the unspecified nature of the vulnerability.
As of now, there is no public information indicating that CVE-2016-4145 has been actively exploited.