Loading vulnerability…
A vulnerability in the Director module (dirapi.dll) of Adobe Shockwave Player before version 11.5.9.615 allows remote attackers to execute arbitrary code or cause a denial of service via a crafted Director movie file. The vulnerability is triggered by a malformed rcsL chunk containing a field whose value is used as a pointer offset, leading to memory corruption. This issue was exploited in the wild in October 2010.
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 (1 hidden).
This repository contains a single Metasploit module targeting a memory corruption vulnerability (CVE-2010-3653) in Adobe Shockwave Player's handling of Director (.DIR) movie files. The exploit is delivered via a malicious HTML page served by the Metasploit HTTP server. When a victim visits the page, a heap spray is performed using JavaScript, and a specially crafted .DIR file is delivered to trigger the vulnerability in the Shockwave ActiveX control. The module supports customizable payloads (such as reverse shells) and is weaponized for use within the Metasploit framework. The main endpoints involved are the HTTP server delivering the exploit and the reference to the vulnerable Shockwave ActiveX control. The exploit is operational against Windows systems running vulnerable versions of Adobe Shockwave Player.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.