CVE-2024-9247
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 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 Annotation objects. The issue results from the lack of proper validation of user-supplied data, which can result in a write before the start of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-24173.
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 confidenceThis is an out-of-bounds write vulnerability in Foxit PDF Reader's Annotation object handling. The flaw results from insufficient validation of user-supplied data during annotation processing, allowing an attacker to write data before the start of an allocated memory object. Successful exploitation enables arbitrary code execution in the context of the current user 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.2.10.53951>= 12.0, <= 12.1.7.15526>= 13.0, <= 13.1.3.22478>= 2023.0, <= 2023.3.0.23028>= 2024.0, <= 2024.2.3.25184<= 2024.2.3.25184CVSS 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.1/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 run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Foxit*"}' in PowerShellAffected if Foxit PDF Reader appears in the installed programs list
-
Determine installed Foxit PDF Reader versionRight-click the Foxit Reader icon, select 'About Foxit Reader' or go to Help > About Foxit Reader to view the exact version numberAffected if The version displayed is 2024.2.3.25184 or lower
-
Check if Foxit PDF Editor is installedOpen Windows Control Panel > Programs and Features, look for 'Foxit Pdf Editor' or 'Foxit PDF Editor' in the list of installed softwareAffected if Foxit PDF Editor appears in the installed programs list
-
Determine installed Foxit PDF Editor versionRight-click the Foxit PDF Editor icon, select 'About Foxit PDF Editor' or go to Help > About to view the exact version numberAffected if The version displayed falls within any of these ranges: <= 11.2.10.53951; >= 12.0 and <= 12.1.7.15526; >= 13.0 and <= 13.1.3.22478; >= 2023.0 and <= 2023.3.0.23028; >= 2024.0 and <= 2024.2.3.25184
You are affected if Foxit PDF Reader version 2024.2.3.25184 or lower is installed, or if Foxit PDF Editor version falls within any of the listed affected version ranges.
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; until then, avoid opening PDF files from untrusted sources and disable automatic opening of PDF files in browsers.
Foxit PDF Reader/Pdf Editor latest version (contact Foxit for exact version numbers or check Foxit.com for the security bulletin)
- Check the Foxit website (www.foxit.com) or Foxit Trust Center for the latest security updates and patches related to CVE-2024-9247
- Download and install the latest version of Foxit PDF Reader or Pdf Editor from the official Foxit website
- Alternatively, verify if your Foxit product has an automatic update feature and run it to get the latest patched version
- Restart the Foxit application after updating
- Ensure the updated version is greater than: 11.2.10.53951, 12.1.7.15526, 13.1.3.22478, 2023.3.0.23028 (for Pdf Editor) or greater than 2024.2.3.25184 (for Pdf Reader)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9247 — 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-9247 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