A memory corruption vulnerability in Adobe Flash Player affects versions before 13.0.0.269 and 14.x through 16.x before 16.0.0.305 on Windows and OS X, and before 11.2.202.442 on Linux. The flaw can be triggered via unspecified vectors and may allow an attacker to execute arbitrary code or cause a denial of service. Publicly available context identifies the issue as distinct from several other Flash vulnerabilities disclosed in the same period, but does not provide the specific vulnerable function, root cause subtype, or trigger mechanism.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module: 'adobe_flash_pcre.rb', which exploits CVE-2015-0318, a vulnerability in Adobe Flash Player's PCRE regex engine. The exploit targets Windows 7 systems running Internet Explorer with Flash Player version 16.0.0.235. The module sets up a browser exploit server that serves a malicious HTML page and SWF file to the victim. When the victim visits the attacker's page, the SWF file is loaded via the Flash ActiveX control, triggering the vulnerability and allowing arbitrary code execution via a PowerShell payload. The payload is customizable and delivered base64-encoded as a FlashVar. The module leverages Metasploit's framework for payload generation and delivery, making it weaponized and easy to use for attackers. The only external endpoint referenced is the official Macromedia Flash CAB file, used to ensure the ActiveX control is present. The actual malicious SWF is loaded from the attacker's server. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.