dbcve.org
Pdf EditorApplication · Foxit

CVE-2022-24908

HIGH · 7.8 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 10.1.7 / 11.2.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader 11.1.0.52543. 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 JP2 images. Crafted data in a JP2 image can trigger a read 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-16187.

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 confidence

A heap-based buffer overread vulnerability exists in Foxit PDF Reader 11.1.0.52543 when parsing JP2 (JPEG 2000) images. The vulnerability allows a remote attacker to read beyond the bounds of an allocated buffer by tricking a user into opening a maliciously crafted PDF file containing specially crafted JP2 image data, potentially leading to arbitrary code execution in the context of the current user process.

MitigationUpdate Foxit PDF Reader to the latest version that patches this vulnerability. Avoid opening PDF files from untrusted sources until the patch is applied.

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
Pdf EditorApplication
Affected:< 10.1.7>= 11.0.0, < 11.2.1
Pdf ReaderApplication
Affected:< 11.2.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Foxit PDF software is installed
    Check for Foxit PDF Reader or Foxit PDF Editor in installed programs list (Control Panel > Programs and Features, or run: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName | findstr Foxit)
    Affected if Foxit PDF Reader or Foxit PDF Editor appears in the installed programs list
  2. Determine installed Foxit version
    Open Foxit PDF Reader/Editor, go to Help > About Foxit PDF Reader/Editor, or right-click the application shortcut and select Properties to view the version information
    Affected if The displayed version cannot be determined or is below 11.2.1 for PDF Reader, or below 10.1.7 / between 11.0.0 and 11.1.x for PDF Editor
  3. Compare version against affected ranges
    Check if the installed version falls into these vulnerable ranges: Foxit PDF Editor versions < 10.1.7, OR versions >= 11.0.0 and < 11.2.1; Foxit PDF Reader versions < 11.2.1
    Affected if The installed version matches any of these vulnerable ranges: < 10.1.7 for PDF Editor, >= 11.0.0 but < 11.2.1 for PDF Editor, or < 11.2.1 for PDF Reader
  4. Identify if JP2 image parsing is in use
    This vulnerability triggers specifically when opening PDF files containing JP2 (JPEG 2000) images. There is no configuration to disable JP2 parsing - the risk exists for any PDF opened with affected versions
    Affected if The affected Foxit version is installed and the user opens PDF files, as JP2 parsing occurs automatically when a PDF containing such images is opened

A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version less than 11.2.1 (for Reader) or within the vulnerable ranges for Editor (< 10.1.7 or >= 11.0.0 and < 11.2.1).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.1.7 / 11.2.1 or later
Fixed in 10.1.711.2.1
Interim mitigation

Update Foxit PDF Reader to the latest version that patches this vulnerability. Avoid opening PDF files from untrusted sources until the patch is applied.

Recommended fix High confidence

Pdf Reader >= 11.2.1; Pdf Editor >= 11.2.1 (or 10.1.7+ if staying on version 10.x)

  1. 1. Open Foxit PDF Reader or PDF Editor application
  2. 2. Navigate to the Help menu
  3. 3. Select 'Check for Updates' or 'About Foxit [Product]' to identify current version
  4. 4. Download and install the latest version from the official Foxit website (www.foxit.com)
  5. 5. Alternatively, download version 11.2.1 or later directly from the Foxit download page
Caveat Minor - typical version upgrade with no major configuration changes expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24908 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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