Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2017-11292 is a high-severity Type Confusion (CWE-843) vulnerability in Adobe Flash Player. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Adobe Flash Player versions 27.0.0.159 and earlier contain a flawed bytecode verification procedure that permits an untrusted value to be used when calculating an array index. This flaw produces a type confusion condition, tracked as CWE-843, that can be leveraged for arbitrary code execution. The vulnerability carries a CVSS 3.1 base score of 8.8 with network attack vector, low complexity, and no required privileges.
An attacker can deliver malicious Flash content over the network that triggers the issue when rendered by the affected player. Successful exploitation grants the attacker the ability to execute arbitrary code in the context of the current user, provided the victim interacts with the content.
Adobe addressed the issue in security bulletin APSB17-32, and corresponding updates were issued through Red Hat (RHSA-2017:2899), Gentoo (GLSA-201710-22), and other distribution channels. Practitioners should apply the vendor-supplied Flash Player updates immediately and consider disabling or removing the plugin where Flash usage is no longer required.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2017-2926
Vulnerability Data
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…
more
to arbitrary code execution.
- CWE(s)
- KEV Date Added
- 03 March 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V3.2.3V15.3.5
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.
Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.
Application security requirements can specify strong typing and interface contracts that reduce type confusion.
Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.
Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.