Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Adobe Flash Player type confusion in bytecode verification

IdentifiersCVE-2017-11292CWE-843· Access of Resource Using…

CVE-2017-11292 is a type confusion vulnerability in Adobe Flash Player 27.0.0.159 and earlier. According to the provided content, the issue is caused by a flawed bytecode verification procedure that permits an untrusted value to be used in the calculation of an array index. This unsafe index handling can corrupt type assumptions during ActionScript/Flash bytecode processing, resulting in type confusion. Successful exploitation can allow an attacker to execute arbitrary code in the context of the affected Flash Player process. The supporting content also indicates the vulnerability was actively targeted by APT28 via exploit delivery before patches were broadly deployed.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in arbitrary code execution on the victim system in the security context of the user running Adobe Flash Player, typically through a malicious web page or embedded Flash content in a document or browser context. In practical terms, this enables delivery and execution of malware, compromise of the endpoint, and follow-on espionage or persistence activity. The content specifically notes that APT28 raced to exploit this vulnerability before patches were deployed, indicating real-world weaponization.

Mitigation

If you can’t patch tonight, do this now.

Until patching or removal is completed, reduce exposure by disabling Adobe Flash Player in browsers and document-rendering workflows, using click-to-play controls, restricting execution of untrusted Flash content, and blocking delivery vectors such as malicious email attachments and links. Enterprise controls such as application allowlisting, browser isolation, least-privilege user contexts, and network filtering for known malicious infrastructure can reduce exploitability and post-exploitation impact. Given the historical in-the-wild exploitation, prioritizing elimination of Flash from the environment is the strongest mitigation.

Remediation

Patch, then assume compromise.

Upgrade Adobe Flash Player to a version newer than 27.0.0.159 that contains Adobe's fix for CVE-2017-11292. Because the vulnerable range explicitly includes 27.0.0.159 and earlier, affected installations should be updated immediately to the vendor-patched release. More broadly, remove or disable Adobe Flash Player where it is no longer required, as Flash has been deprecated and is no longer supported.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdobeFlash Playerapplication
AdobeFlash Player Desktop Runtimeapplication
Red HatEnterprise Linux Desktopoperating_system
Red HatEnterprise Linux Serveroperating_system
Red HatEnterprise Linux Workstationoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence1

Every observed campaign linking this CVE to a named adversary.

Associated malware3

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.