CVE-2017-11292
Adobe Flash Player Type Confusion
- Published22 Oct 2017
- Added to CISA KEV3 Mar 2022
- Remediation due24 Mar 2022
Description
Adobe Flash Player version 27.0.0.159 and earlier has a flawed bytecode verification procedure, which allows for an untrusted value to be used in the calculation of an array index. This can lead to type confusion, and successful exploitation could lead to arbitrary code execution.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/errata/RHSA-2017:2899
- https://helpx.adobe.com/security/products/flash-player/apsb17-32.html
- https://security.gentoo.org/glsa/201710-22
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-11292
- http://www.securityfocus.com/bid/101286
- http://www.securitytracker.com/id/1039582
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2017-11292 being actively exploited?
Yes. CVE-2017-11292 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Mar 2022.
How severe is CVE-2017-11292?
CVE-2017-11292 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 11.9% probability of exploitation.
Which products are affected by CVE-2017-11292?
Affected products include Adobe Flash Player, Adobe Flash Player Desktop Runtime, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.
How do I fix CVE-2017-11292?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2017-11292 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.