Loading vulnerability…
A stack-based buffer overflow exists in Foxit Reader 3.0 (builds 1120 and 1301) in the handling of the filename argument for the 'Open/Execute a file' action in PDF files. By supplying an overly long relative or absolute path as the filename, an attacker can trigger a buffer overflow, leading to memory corruption. This vulnerability can be exploited remotely via a maliciously crafted PDF file, potentially allowing arbitrary code execution with the privileges of the user running Foxit Reader. The vulnerability was discovered by Francisco Falcón of Core Security.
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: 'Foxit Reader 3.0 Open Execute Action Stack Based Buffer Overflow'. The module exploits a stack-based buffer overflow vulnerability (CVE-2009-0837) in Foxit Reader 3.0 (build 1301 and earlier) on Windows XP SP2. The exploit works by generating a specially crafted PDF file ('msf.pdf') that, when opened by a vulnerable version of Foxit Reader, triggers the overflow via a malicious 'Launch' action, allowing arbitrary code execution. The module allows the attacker to embed a customizable Metasploit payload (up to 1024 bytes, with certain bad characters filtered) into the PDF. The attack vector is local, requiring the victim to open the malicious file. The repository is structured as a standard Metasploit exploit module written in Ruby, and does not contain any network endpoints or external URLs beyond references in the module metadata.
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.