CVE-2024-30348
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 U3D File Parsing Out-Of-Bounds Write 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 parsing of U3D files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22911.
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 confidenceFoxit PDF Reader contains an out-of-bounds write vulnerability in its U3D (Universal 3D) file parser. The vulnerability stems from insufficient validation of user-supplied data during U3D parsing, allowing writes beyond the boundaries of allocated memory buffers. An attacker can exploit this by tricking a user into opening a malicious PDF file containing a specially crafted U3D object, enabling arbitrary code execution in the context of the current process.
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.0601, <= 12.1.2.55366>= 13.0.0.61829, <= 13.0.1.61866>= 2023.1.0.55583, <= 2023.3.0.63083<= 10.1.12.37872>= 11.0.0.49893, <= 11.2.8.53842>= 12.0.0.12394, <= 12.1.4.15400>= 13.0.0.21632, <= 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.
-
Verify Foxit PDF product is installedCheck for Foxit PDF Reader or Foxit PDF Editor in the installed programs list. On Windows, open Control Panel > Programs and Features, or search for 'Foxit' in the Start menu.Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine the installed version numberOpen Foxit, then go to Help > About Foxit PDF Reader (or About Foxit PDF Editor). The version number is displayed in the dialog box.Affected if The version displayed matches any of the affected ranges listed in the CVE (for Reader: <= 2023.3.0.63083 or <= 2023.3.0.23028; for Editor: multiple ranges including versions <= 11.1.6.0109, 12.x versions between 12.0.0.0601-12.1.2.55366, 13.x versions between 13.0.0.61829-13.0.1.61866, 2023.x versi
-
Confirm U3D parsing is reachableThe vulnerability triggers when parsing U3D (Universal 3D) objects embedded in PDF files. There is no separate configuration to disable this check - the vulnerability exists in the core U3D parser used when opening any PDF containing 3D content.Affected if The installed Foxit version falls within the affected version ranges, meaning opening a specially crafted PDF with a malicious U3D object could trigger the out-of-bounds write
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed and the version number falls within any of the affected version ranges specified in the CVE.
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 from Foxit when available. Until then, avoid opening PDF files from untrusted sources and disable the Foxit PDF Reader plugin in web browsers to prevent drive-by attacks via malicious web pages.
Latest available Foxit PDF Reader/PDF Editor (2024 or latest stable release)
- 1. Navigate to the official Foxit download page at https://www.foxit.com/downloads/
- 2. Download the latest version of Foxit PDF Reader or Foxit PDF Editor based on your installed product
- 3. Uninstall the current version of Foxit PDF software from your system
- 4. Install the newly downloaded latest version of the software
- 5. After installation, verify the version by clicking Help > About Foxit PDF Reader or About Foxit PDF Editor
- 6. Ensure automatic updates are enabled by going to File > Preferences > General > Check for updates automatically
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30348 — 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-30348 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