PhantompdfApplication · Foxitsoftware

CVE-2020-12248

HIGH · 8.8 CVSS v3.1 Published 2020-09-04
Fix available
A fix is available. Upgrade to after 10.0.0.35798 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
In Foxit Reader and PhantomPDF before 10.0.1, and PhantomPDF before 9.7.3, attackers can execute arbitrary code via a heap-based buffer overflow because dirty image-resource data is mishandled.

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 · moderate confidence

Heap-based buffer overflow in Foxit Reader and PhantomPDF allows arbitrary code execution due to mishandling of dirty image-resource data. The vulnerability affects versions before 10.0.1 (both products) and PhantomPDF before 9.7.3. Attackers can exploit this by crafting malicious PDF files with specially crafted image resources that overflow heap buffers during parsing.

MitigationUpdate Foxit Reader to version 10.0.1 or later and PhantomPDF to version 9.7.3 or later to obtain the patched software. Consider disabling JavaScript in Reader settings as a defense-in-depth measure until updates can be deployed.

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
PhantompdfApplication
Affected:<= 9.7.2.29539<= 10.0.0.35798
ReaderApplication
Affected:<= 10.0.0.35798

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Identify installed Foxit product
    Check for Foxit Reader or PhantomPDF installation by reviewing installed programs in Windows Control Panel > Programs and Features, or run 'Get-ItemProperty' on registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* to list installed applications and look for 'Foxit Reader' or 'Foxit PhantomPDF' entries.
    Affected if Either Foxit Reader or Foxit PhantomPDF is present on the system.
  2. Retrieve Foxit Reader version
    If Foxit Reader is installed, find its version by right-clicking the Foxit Reader shortcut, selecting Properties, and viewing the 'Details' tab, or by checking the file version of the executable (typically in C:\Program Files (x86)\Foxit Software\Foxit Reader\FoxitReader.exe).
    Affected if The version retrieved is less than or equal to 10.0.0.35798.
  3. Retrieve PhantomPDF version
    If Foxit PhantomPDF is installed, find its version by right-clicking the PhantomPDF shortcut, selecting Properties, and viewing the 'Details' tab, or by checking the file version of the executable (typically in C:\Program Files (x86)\Foxit Software\PhantomPDF\PhantomPDF.exe).
    Affected if The version retrieved is less than or equal to 9.7.2.29539 or less than or equal to 10.0.0.35798.
  4. Confirm vulnerable image parsing is possible
    This vulnerability triggers when opening a PDF containing specially crafted 'dirty' image-resource data. The flaw exists in the parsing logic and does not require a specific configuration toggle; it is present in all affected versions when processing such malformed PDFs.
    Affected if An affected version of Foxit Reader (10.0.0.35798 or earlier) or PhantomPDF (9.7.2.29539 or earlier, or 10.0.0.35798 or earlier) is installed and processes PDF files.

You are affected if Foxit Reader version 10.0.0.35798 or earlier, or Foxit PhantomPDF version 9.7.2.29539 or earlier (or 10.0.0.35798 or earlier) is installed on your system.

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.

From vendor data
Upgrade available Upgrade to a release after 10.0.0.35798
Interim mitigation

Update Foxit Reader to version 10.0.1 or later and PhantomPDF to version 9.7.3 or later to obtain the patched software. Consider disabling JavaScript in Reader settings as a defense-in-depth measure until updates can be deployed.

Fix this in Phantompdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12248 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-12248 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