CVE-2016-4217: Critical severity adobe flash player vulnerability

Published Jul 13, 2016
·
Updated

Adobe Flash Player before 18.0.0.366 and 19.x through 22.x before 22.0.0.209 on Windows and OS X and before 11.2.202.632 on Linux allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than 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-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, and CVE-2016-4246.

Affected Software

12 affected components
Adobe Flash Player Desktop Runtime<=22.0.0.192
Apple iOS and macOS
Microsoft Windows
Adobe Flash Player<=18.0.0.360
Adobe Flash Player Chrome<=22.0.0.192
Google Chrome OS
Linux Linux kernel
Adobe Flash Player Edge<=22.0.0.192
Adobe Flash Player Internet Explorer<=22.0.0.192
Microsoft Windows 10
Microsoft Windows 8.1
Adobe Flash Player<=11.2.202.626

Event History

Jul 13, 2016
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-4217?

CVE-2016-4217 has a critical severity rating due to its potential for arbitrary code execution and denial of service.

2

How do I fix CVE-2016-4217?

To fix CVE-2016-4217, users should update to Adobe Flash Player version 22.0.0.209 or later.

3

What versions of Adobe Flash Player are affected by CVE-2016-4217?

CVE-2016-4217 affects Adobe Flash Player versions prior to 18.0.0.366 and versions 19.x through 22.x before 22.0.0.209.

4

Can CVE-2016-4217 cause a denial of service?

Yes, CVE-2016-4217 can lead to denial of service due to memory corruption vulnerabilities.

5

Is there any workaround for CVE-2016-4217?

There are no effective workarounds for CVE-2016-4217; updating to the latest version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203