CVE-2022-25108
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 and Editor before 11.2.1 and PhantomPDF before 10.1.7 allow a NULL pointer dereference during PDF parsing because the pointer is used without proper validation.
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 confidenceA NULL pointer dereference vulnerability exists in Foxit PDF Reader and Editor before 11.2.1 and PhantomPDF before 10.1.7. During PDF parsing, a pointer is used without proper validation, which can lead to a denial of service through application crash.
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, < 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Identify installed Foxit product and versionOn Windows, open the application and go to Help > About Foxit Reader/Editor to view the exact version number. Alternatively, check the Windows Programs and Features list or the registry key under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Foxit entries.Affected if The version shown is less than 10.1.7, or falls between 11.0.0 and 11.2.0 inclusive (for Foxit PDF Editor), or less than 11.2.1 (for Foxit PDF Reader).
-
Confirm PhantomPDF installation and versionCheck if PhantomPDF is installed by looking in Programs and Features, or by searching for PhantomPDF in the Start menu. If found, note the version from Help > About.Affected if PhantomPDF version is below 10.1.7.
-
Determine if PDF parsing feature is accessibleVerify that the Foxit application can open and parse PDF files. This is the default behavior when double-clicking a PDF file or opening one within the application.Affected if The application can open PDF files, which triggers the parsing routine where the NULL pointer dereference occurs.
A user is affected if they have Foxit PDF Reader/Editor version below 11.2.1, Foxit PDF Editor version below 10.1.7, or PhantomPDF version below 10.1.7, and routinely open PDF documents with the application.
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 and Editor to version 11.2.1 or later, and PhantomPDF to version 10.1.7 or later.
Foxit PDF Reader/Editor version 11.2.1 or later (or 10.1.7 for PhantomPDF)
- Navigate to the official Foxit website at www.foxit.com
- Locate the download section for Foxit PDF Reader or Foxit PDF Editor (PhantomPDF)
- Download the latest version (11.2.1 or later for both products)
- Run the installer and follow the prompts to upgrade
- Restart any running instances of Foxit PDF software after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25108 — 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-25108 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