CVE-2022-24907
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 · uneditedThis 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-16186.
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 confidenceFoxit PDF Reader 11.1.0.52543 contains an out-of-bounds read vulnerability in its JP2 image parser. By crafting malicious JP2 image data embedded in a PDF file or web page, an attacker can read beyond the bounds of an allocated buffer, potentially achieving arbitrary code execution within 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.7>= 11.0.0, < 11.2.1< 11.2.1CVSS 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.
-
Confirm Foxit PDF Reader installationOpen Windows Settings > Apps > Installed Apps (or Programs and Features in Control Panel) and search for 'Foxit Reader' or 'Foxit PDF 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 appears in the installed programs list.
-
Identify installed Foxit versionLaunch Foxit PDF Reader, then go to Help > About Foxit Reader (or press F9). The version number will be displayed in the dialog box. Alternatively, right-click the Foxit Reader shortcut, select Properties, and check the Details tab for the product version.Affected if The version number is less than 11.2.1 (for example, 11.1.0.52543 or earlier, or any version 10.x.x).
-
Verify JP2 image parsing capabilityThe JP2 (JPEG 2000) image parser is a built-in component of Foxit PDF Reader and activates automatically when opening PDF files containing JP2 images. There is no separate enable/disable toggle for this feature in standard configurations.Affected if The JP2 parser is present in all standard Foxit PDF Reader installations and activates upon opening a PDF file containing JP2 image data.
-
Inspect PDF files for JP2 image contentOpen PDF files in Foxit PDF Reader, then use the Navigation Pane (Ctrl+6) to view embedded images, or use File > Properties > Description to examine the document. You can also check using command-line tools like pdfinfo (from XPDF) or similar utilities to identify if a PDF contains JP2/JPEG2000 streams.Affected if The user has PDF files that contain embedded JP2 (JPEG 2000) images.
A user is affected if Foxit PDF Reader version is below 11.2.1 and they open PDF files or view web pages containing specially crafted JP2 image data that triggers the out-of-bounds read vulnerability.
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 · scoped10.1.711.2.1
Update Foxit PDF Reader to the latest patched version. Avoid opening untrusted PDF files or visiting malicious web pages that could deliver specially crafted JP2 images.
Foxit PDF Reader 11.2.1 or later / Foxit PDF Editor 10.1.7 or later (or 11.2.1+ for 11.x branch)
- 1. Navigate to the official Foxit website (www.foxit.com) and navigate to the Downloads section for either PDF Reader or PDF Editor
- 2. Download the fixed version: PDF Reader 11.2.1 or later, or PDF Editor 10.1.7 or later (or 11.2.1 or later for the 11.x branch)
- 3. Close any running instances of Foxit PDF Reader or PDF Editor
- 4. Run the installer and follow the prompts to install the updated version
- 5. After installation, verify the version by going to Help > About Foxit [Reader/Editor] to confirm the installed version is 11.2.1 or later (or 10.1.7 for the 10.x Editor branch)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24907 — 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-2022-24907 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