CVE-2024-30343
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 Reader Annotation Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. 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-22721.
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 confidenceUse-After-Free vulnerability in Foxit PDF Reader's Annotation object handling. The flaw results from lack of validating object existence before performing operations, leading to memory corruption that can be leveraged for remote code execution in the current process context.
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<= 11.1.6.0109>= 12.0.0, <= 12.1.2.55366>= 13.0.0, <= 13.0.1.61866>= 2023.1.0.55583, <= 2023.3.0.63083<= 11.2.8.53842>= 12.0.0, <= 12.1.4.15400>= 13.0.0, <= 13.0.1.21693>= 2023.1.0.15510, <= 2023.3.0.23028<= 2023.3.0.63083<= 2023.3.0.23028CVSS 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.
-
Check if Foxit PDF software is installedOpen Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Foxit*'}Affected if Foxit PDF Reader or Foxit PDF Editor appears in the installed programs list
-
Identify the specific Foxit product and versionRight-click the Foxit application icon, select Properties, and view the Details tab to see the Version field. Alternatively, locate the executable (FoxitReader.exe or FoxitPDFEditor.exe) in the installation directory, right-click, and view Properties > DetailsAffected if The product is Foxit PDF Reader or Foxit PDF Editor with a version number that matches the affected ranges provided
-
Compare installed version against affected ranges for Foxit PDF ReaderFor PDF Reader, check if version is <= 2023.3.0.63083 or <= 2023.3.0.23028. These are the vulnerable versions based on the CVE dataAffected if The installed PDF Reader version falls within or below these version numbers, meaning it is affected
-
Compare installed version against affected ranges for Foxit PDF EditorFor PDF Editor, check if version matches any of these vulnerable ranges: <= 11.1.6.0109; >= 12.0.0 <= 12.1.2.55366; >= 13.0.0 <= 13.0.1.61866; >= 2023.1.0.55583 <= 2023.3.0.63083; <= 11.2.8.53842; >= 12.0.0 <= 12.1.4.15400; >= 13.0.0 <= 13.0.1.21693; >= 2023.1.0.15510 <= 2023.3.0.23028Affected if The installed PDF Editor version falls within any of these version ranges, meaning it is affected
-
Determine if PDF files with annotations are processedThe vulnerability specifically exists in Annotation object handling. Opening any PDF file that uses Foxit's annotation features (comments, highlights, notes, forms) triggers the vulnerable code pathAffected if The user opens PDF documents containing annotation objects in the affected Foxit application
A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version matching any of the affected ranges and the application processes PDF files containing annotation objects.
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 vendor patches from Foxit when available; avoid opening untrusted PDF files or visiting malicious websites until the vulnerability is patched.
Latest stable Foxit PDF Reader/PDF Editor release (contact Foxit support or check security advisory for exact fixed version numbers)
- 1. Visit the official Foxit website download page at www.foxit.com to obtain the latest version of Foxit PDF Reader or PDF Editor.
- 2. Identify your current installed version by opening Foxit PDF Reader, clicking 'Help' in the menu bar, then selecting 'About Foxit PDF Reader' to confirm the exact version number.
- 3. Download the most recent stable release available for your product (either PDF Reader or PDF Editor depending on what is installed).
- 4. Close all instances of Foxit PDF Reader/PDF Editor before running the installer.
- 5. Run the installer and follow the prompts to complete the upgrade.
- 6. After installation, verify the new version by checking 'Help' > 'About Foxit PDF Reader' to confirm the version is beyond the affected ranges (above 11.1.6.0109, 12.1.2.55366, 13.0.1.61866, or 2023.3.0.63083 depending on your product line).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30343 — 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-2024-30343 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