CVE-2024-9248
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 PDF 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 PDF 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-24300.
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 PDF file parsing engine. The lack of proper validation of user-supplied data during PDF parsing allows an attacker to write past the end of an allocated buffer, enabling 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 Settings > Apps > Apps & features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Foxit*Reader*'}. Alternatively, check common installation paths like C:\Program Files\Foxit Software\Foxit Reader\ or C:\Program Files (x86)\Foxit Software\Foxit Reader\Affected if Foxit PDF Reader is found on the system
-
Determine the installed Foxit PDF Reader versionIf installed, right-click the Foxit Reader executable in the installation folder, select Properties, and view the Details tab for the Version field. Or use PowerShell: (Get-Item 'C:\Program Files\Foxit Software\Foxit Reader\FoxitReader.exe').VersionInfo.FileVersionAffected if Version is <= 2024.2.3.25184
-
Check if Foxit PDF Editor is installedOpen Windows Settings > Apps > Apps & features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Foxit*PDF*Editor*'}. Check installation folders like C:\Program Files\Foxit Software\Foxit PDF Editor\Affected if Foxit PDF Editor is found on the system
-
Determine the installed Foxit PDF Editor versionRight-click the FoxitPDFEditor.exe executable in the installation folder, select Properties, and view the Details tab for the Version field. Or use PowerShell: (Get-Item 'C:\Program Files\Foxit Software\Foxit PDF Editor\FoxitPDFEditor.exe').VersionInfo.FileVersionAffected if Version 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 is <= 2024.2.3.25184 OR Foxit PDF Editor version is within any of the affected version ranges listed, and you open 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.
dbcve · scopedUpdate Foxit PDF Reader to the latest version once available. Avoid opening untrusted PDF files and implement email/mail filtering for attachments.
Foxit Pdf Reader 2024.2.4 or later; Foxit Pdf Editor 11.2.11/12.1.8/13.1.4/2023.3.1 or later (matching your product line)
- 1. Determine the currently installed Foxit product (Pdf Reader or Pdf Editor) and its exact version number via Help > About
- 2. Navigate to the official Foxit software download page or check Foxit security advisories at www.foxit.com for the latest fixed version
- 3. Download the latest version of Foxit Pdf Reader or Pdf Editor that corresponds to your product line
- 4. Close all instances of Foxit PDF applications before installation
- 5. Run the installer for the new version and complete the installation process
- 6. Verify the installed version matches or exceeds the fixed release (for Reader: >2024.2.3.25184, for Editor: >11.2.10.53951 or >12.1.7.15526 or >13.1.3.22478 or >2023.3.0.23028 depending on your product line)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9248 — 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-9248 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