CVE-2024-30349
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-22912.
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 · moderate confidenceThis is an out-of-bounds write vulnerability in Foxit PDF Reader's U3D (Universal 3D) file parser. The vulnerability results from insufficient validation of user-supplied data during U3D file parsing, allowing a write operation past the end of an allocated buffer. An attacker can exploit this by tricking a user into opening a malicious PDF file, achieving remote 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<= 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.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.
-
Confirm Foxit PDF product is installedCheck for Foxit PDF Reader or Foxit PDF Editor in the system: look for the application in Program Files (e.g., C:\Program Files\Foxit Software\Foxit Reader or Foxit PDF Editor), or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Foxit'Affected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine installed Foxit versionOpen Foxit and navigate to Help > About Foxit Reader (or About Foxit PDF Editor), or right-click the executable file (FoxitReader.exe or FoxitPDFEditor.exe) in Program Files and select Properties > Details to view the File VersionAffected if The displayed version falls within any of the affected ranges: <= 10.1.12.37872; >= 11.0.0.49893 and <= 11.2.8.53842; >= 12.0.0.12394 and <= 12.1.4.15400; >= 13.0.0.21632 and <= 13.0.1.21693; >= 2023.1.0.15510 and <= 2023.3.0.23028 for Editor, or <= 2023.3.0.23028 for Reader
-
Check if U3D rendering is enabledIn Foxit, go to File > Preferences > Page Display (or Settings > Preferences > 3D), look for options related to 'U3D' or '3D content' or 'Universal 3D' rendering. On Windows, the preference may also be stored in the registry under HKCU\Software\Foxit Software\Foxit Reader\Preferences or in the application config file in the AppData folderAffected if U3D/3D rendering or parsing is enabled in the application settings (the vulnerability only triggers when parsing U3D content in a PDF)
-
Identify recent PDF files openedCheck the application's recent files list (File > Open Recent) or Windows Jump List for recently opened PDF files, or examine the Windows Temp folder and Foxit's temp folder (%LOCALAPPDATA%\Foxit\Foxit Reader\Temp) for suspicious PDF filesAffected if Any PDF files from untrusted sources were recently opened, as the exploit requires a maliciously crafted PDF with U3D content
The system is affected if Foxit PDF Reader (any version <= 2023.3.0.23028) or Foxit PDF Editor (any version matching the affected ranges) is installed with U3D/3D rendering enabled and the user may have opened untrusted 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.
From vendor dataApply the vendor patch from Foxit when available. Until then, train users to avoid opening PDF files from untrusted sources and consider disabling U3D rendering in Foxit settings if the feature is not required.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30349 — 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-30349 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