Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Type Confusion RCE in Adobe Flash Player bytecode verification

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

CVE-2017-11292 is a vulnerability in Adobe Flash Player 27.0.0.159 and earlier caused by a flawed bytecode verification procedure. According to the provided content, the verifier allows an untrusted value to be used in the calculation of an array index, which can result in type confusion. The content further notes exploitation involving the vulnerable mediacore.BufferControlParameters class. Successful exploitation can corrupt program state and achieve arbitrary code execution. Public reporting cited in the content shows the flaw was weaponized in malicious Microsoft Word documents embedding Flash content, including DealersChoice.B-based delivery used by APT28, with observed exploitation on Windows 7 and Windows 10 systems running vulnerable Flash and Office 2013 combinations.

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 lead to arbitrary code execution in the context of the affected application/user. In observed campaigns, attackers used the flaw to execute a follow-on payload after the exploit retrieved, decrypted, and launched code from a remote server. The content indicates this enabled delivery of the APT28 Uploader implant for reconnaissance and subsequent deployment of additional tools. Because the flaw affected Flash Player across Windows, macOS, Linux, and Chrome OS, the potential impact extended broadly to systems running vulnerable Flash versions.

Mitigation

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

Until patching/removal is completed, reduce exposure by disabling or uninstalling Adobe Flash Player, blocking or restricting Flash execution in Microsoft Office documents and browsers, and preventing embedded ActiveX/Flash content from running in Office attachments received via email. The content notes exploitation via malicious Word documents with embedded Flash objects, so email attachment filtering, sandboxing, and detonation of Office documents are relevant mitigations. The content also notes that users running 64-bit Microsoft Office 2016 and Windows 10 RS3 appeared protected against the observed exploit chain, but this should not be treated as a substitute for patching.

Remediation

Patch, then assume compromise.

Apply Adobe's security update that patched CVE-2017-11292. The content states Adobe announced and patched the vulnerability on 2017-10-16 and specifically identifies Flash Player 27.0.0.159 and earlier as affected. Upgrading to a patched Flash Player release is the primary remediation. Organizations should also remove or retire Adobe Flash Player where still present, given its historical exploitability and end-of-life status.
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 evidence3

Every observed campaign linking this CVE to a named adversary.

Associated malware5

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.