CVE-2021-34962
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFoxit PDF Editor Caret Annotation Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Editor. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of Annotation objects. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14364.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCVE-2021-34962 is a use-after-free vulnerability in Foxit PDF Editor's Caret Annotation handling. The vulnerability stems from the lack of validation of object existence before performing operations on Annotation objects, allowing an attacker to free memory and then use the dangling pointer to execute arbitrary code in the context of the current process. Exploitation requires user interaction, specifically opening a malicious PDF file.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.1.5.37672= 11.0.0.49893= 11.0.1.49938<= 11.0.1.49938CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Foxit applicationCheck for Foxit PDF Editor or Foxit PDF Reader in installed programs (Control Panel > Programs and Features on Windows, or check Applications folder on macOS)Affected if Either Foxit PDF Editor or Foxit PDF Reader is installed
-
Determine installed version of Foxit PDF EditorOpen Foxit PDF Editor, click Help > About Foxit PDF Editor, or right-click the application in Programs and Features and select 'Change' or 'Properties' to view versionAffected if Version is <= 10.1.5.37672, or equals 11.0.0.49893, or equals 11.0.1.49938
-
Determine installed version of Foxit PDF ReaderOpen Foxit PDF Reader, click Help > About Foxit PDF Reader, or check the application's properties to view versionAffected if Version is <= 11.0.1.49938 (any version up to and including this release)
-
Assess PDF opening behaviorInterview users or review endpoint monitoring logs to determine if users open PDF files from untrusted or unknown sourcesAffected if Users routinely open PDF files from email attachments, downloads, or other untrusted sources without prior validation
A user is affected if Foxit PDF Editor version is 10.1.5.37672 or earlier, or exactly 11.0.0.49893 or 11.0.1.49938, or Foxit PDF Reader version is 11.0.1.49938 or earlier, and the application is used to open PDF files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patch by updating Foxit PDF Editor to the latest version. Until patched, instruct users to avoid opening PDF files from untrusted sources and consider running the application with reduced privileges.
Foxit PDF Editor/PDF Reader version 11.0.2 or later
- 1. Close all instances of Foxit PDF Editor or Foxit PDF Reader.
- 2. Navigate to the official Foxit website at www.foxit.com to download the latest version.
- 3. Download and install the most recent stable version of Foxit PDF Editor and/or Foxit PDF Reader.
- 4. Verify the installed version matches or exceeds the fixed release (version 11.0.2 or later).
- 5. Restart the application and confirm it launches without errors.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data