Loading vulnerability…
A buffer overflow vulnerability exists in Adobe Illustrator CS4 14.0.0, CS3 13.0.3 and earlier, and CS3 13.0.0, which allows remote attackers to execute arbitrary code by supplying a specially crafted Encapsulated PostScript (.eps) file containing an overly long DSC comment. The vulnerability is triggered during the parsing of the DSC comment, leading to memory corruption and potential code execution.
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 (2 hidden).
This repository contains a single Metasploit module targeting a buffer overflow vulnerability (CVE-2009-4195) in Adobe Illustrator CS4 (v14.0.0) when processing Encapsulated Postscript (.eps) files with overlong DSC comments. The exploit is implemented in Ruby and leverages the Metasploit framework's FILEFORMAT exploit mixin. The module generates a malicious EPS file (default name: msf.eps) containing a large buffer, a return address (CALL ESI in icudt36.dll), and a customizable payload (up to 1000 bytes, avoiding certain bad characters). The exploit is triggered when a victim opens the crafted EPS file in a vulnerable version of Adobe Illustrator, resulting in arbitrary code execution. The module is fully weaponized, allowing the attacker to select and encode payloads using Metasploit's payload system. No network endpoints are involved; the attack vector is local, requiring user interaction to open the malicious file. The repository structure is typical for Metasploit modules, with all logic contained in a single Ruby file under the appropriate directory.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.