Stack-based Buffer Overflow in Foxit Reader 3.0 Open/Execute Action
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary code on the target system with the privileges of the current user. The attacker can craft a PDF file with a maliciously long filename in an Open/Execute action, which, when opened in a vulnerable version of Foxit Reader, results in memory corruption and control over program execution flow. This can be further facilitated by heap spraying via embedded JavaScript in the PDF.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, block or restrict the opening of untrusted PDF files, especially those containing embedded actions or JavaScript. Disable JavaScript execution in Foxit Reader where feasible. Employ endpoint security solutions to detect and block exploitation attempts.
Patch, then assume compromise.
Upgrade Foxit Reader to version 3.0 build 1506 or later, which includes proper length checks on the filename argument and introduces user prompts for local file execution. Ensure all users are running a non-vulnerable version.
1 exploit validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.