CVE-2010-20010: Foxit PDF Reader < 4.2.0.0928 Title Stack Buffer Overflow
Foxit PDF Reader before 4.2.0.0928 does not properly bound-check the /Title entry in the PDF Info dictionary. A specially crafted PDF with an overlong Title string can overflow a fixed-size stack buffer, corrupt the Structured Exception Handler (SEH) chain, and lead to arbitrary code execution in the context of the user who opens the file.
Security readout for executives and security teams
Plain-English summary
This is a malicious-PDF risk in older Foxit PDF Reader. If a user opens a crafted PDF, its title metadata can overflow memory and run code as that user. The bundle cites public exploit references, but does not show confirmed active exploitation.
Executive priority
Treat as high priority where legacy Foxit Reader exists, especially on workstations handling external PDFs. The business risk is user-driven code execution from a document, with public exploit material available. Prioritize discovery and removal or upgrade of affected legacy installs.
Technical view
Foxit PDF Reader before 4.2.0.0928 improperly bounds-checks the PDF Info dictionary /Title entry. An overlong Title string can trigger a stack buffer overflow, corrupt SEH, and allow code execution in the opening user's context. The CVE maps to CWE-121 and CVSS 4.0 score 8.4.
Likely exposure
Exposure is likely limited to endpoints still running legacy Foxit PDF Reader versions before 4.2.0.0928. The affected-version metadata in the bundle is incomplete or inconsistent, so validate against installed product versions rather than relying only on CPE data.
Exploitation context
The attack requires user interaction: opening a specially crafted PDF. Public exploit references are cited, including Exploit-DB and a Metasploit module. KEV is false in the bundle, and no cited source confirms current active exploitation.
Researcher notes
Focus validation on version exposure and document-handling paths. The bundle supports public exploit availability, but not active exploitation. Avoid over-relying on the affected array because it lists version “0” and default unaffected despite the narrative stating before 4.2.0.0928.
Mitigation direction
Upgrade Foxit PDF Reader to 4.2.0.0928 or later per vendor guidance.
Remove unsupported legacy Foxit Reader installs from managed endpoints.
Harden email and web controls for suspicious PDF attachments and downloads.
Restrict risky file-opening workflows for users who handle untrusted documents.
Check Foxit guidance for any additional vendor-recommended remediation.
Validation and detection
Inventory endpoints for Foxit PDF Reader installations and exact versions.
Flag any Foxit Reader versions earlier than 4.2.0.0928.
Confirm legacy Foxit is not the default PDF handler.
Review EDR, email, and proxy alerts for suspicious PDF activity.
Validate remediation through software inventory after upgrades or removals.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.