CVE-2020-7374 is a stack-based buffer overflow in Documalis Free PDF Editor 5.7.2.26 and Documalis Free PDF Scanner 5.7.2.122. The vulnerable condition arises because the applications do not appropriately validate the contents of JPEG images embedded within a PDF document. A specially crafted PDF containing malformed or malicious JPEG data can trigger memory corruption on the stack during parsing or processing of the embedded image, which may allow arbitrary code execution in the context of the user running the affected software.
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 targeting a stack buffer overflow vulnerability (CVE-2020-7374) in Documalis Free PDF Editor v5.7.2.26 and Documalis Free PDF Scanner v5.7.2.122 on Windows 7 and Windows 10. The exploit works by generating a malicious PDF file (default name: msf.pdf) containing a specially crafted JPEG image. When the PDF is opened in the vulnerable application, the JPEG image triggers a buffer overflow, allowing execution of arbitrary code as the user. The module allows the attacker to specify any Metasploit payload (up to 1715 bytes), providing remote code execution. The exploit is operational and requires social engineering to convince a user to open the malicious PDF. The repository is structured as a single Ruby file compatible with the Metasploit framework, and does not contain any network endpoints, but targets local file processing in the vulnerable applications.
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.