CVE-2024-30355
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 AcroForm 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 handling of Doc objects in AcroForms. 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-22809.
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 confidenceOut-of-bounds write vulnerability in Foxit PDF Reader's AcroForm Doc object handling. The application fails to properly validate user-supplied data when processing AcroForms, allowing writes beyond allocated buffer boundaries. This memory corruption can be leveraged for 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<= 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.
-
Check if Foxit PDF Reader is installedOpen Windows Control Panel > Programs and Features, or check C:\Program Files\Foxit Software\ for Foxit Reader or Foxit Editor directoriesAffected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine the installed Foxit versionIn Foxit, click Help > About Foxit PDF Reader (or Editor) to display the version number and build informationAffected if The displayed version falls within any of these 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)
-
Verify AcroForm functionality is accessibleOpen any PDF file in Foxit and check if Form filling or form field interaction is available via the Forms menu or toolbarAffected if AcroForm features are enabled and the Foxit version is within the affected ranges listed above
The environment is affected if Foxit PDF Reader (version <= 2023.3.0.23028) or Foxit PDF Editor (any version within the specified ranges) is installed with AcroForm functionality accessible.
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 vendor-supplied patch from Foxit (upgrade to latest version); avoid opening untrusted PDF files or visiting malicious pages until patch is applied.
- 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-2024-30355 — 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-30355 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