CVE-2010-20010 is a stack-based buffer overflow in Foxit PDF Reader before 4.2.0.0928. The vulnerability is triggered when the application parses the /Title entry in the PDF Info dictionary without proper bounds checking. A specially crafted PDF containing an overlong Title string can overflow a fixed-size stack buffer and corrupt the Structured Exception Handler (SEH) chain, which can be leveraged to achieve arbitrary code execution when the victim opens the malicious PDF.
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 (foxit_title_bof.rb) that exploits a stack buffer overflow vulnerability in Foxit PDF Reader versions prior to 4.2.0.0928 (specifically tested on 4.1.1 for Windows). The exploit works by generating a malicious PDF file with an overly long Title field, which triggers the overflow when opened in the vulnerable application. The module leverages Metasploit's payload system, allowing the attacker to select and encode arbitrary shellcode, which is delivered via the crafted PDF. The exploit does not use JavaScript and instead relies on direct manipulation of the PDF structure and the Title metadata. The only fingerprintable endpoint is the malicious PDF file itself (default name: corelan_foxit.pdf). The code is written in Ruby and is structured as a standard Metasploit exploit module, making use of several Metasploit mixins for file format and PDF manipulation. The exploit is operational and can be used to achieve code execution on vulnerable systems when a user opens the generated PDF 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 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.