PhantompdfApplication · Foxitsoftware

CVE-2019-17142

HIGH · 8.8 CVSS v3.1 Published 2019-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PhantomPDF 9.6.0.25114. 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 processing of script within a Keystroke action of a listbox field. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-9081.

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

This is a use-after-free/null pointer dereference vulnerability in Foxit PhantomPDF where the application fails to validate object existence before performing operations on it. Specifically, script processing within a Keystroke action of a listbox field lacks proper validation, allowing remote code execution in the context of the current process when a user opens a malicious PDF.

MitigationApply the vendor patch/update to Foxit PhantomPDF to the latest version. Until patched, warn users not to open PDF files from untrusted sources and consider disabling JavaScript execution in PDF settings.

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.6.0.25114

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. Check Foxit PhantomPDF installed version
    Open Foxit PhantomPDF, then go to Help > About Foxit PhantomPDF. Alternatively, check Add/Remove Programs (Windows) or the application's executable properties. Look for the version number displayed.
    Affected if The installed version is 9.6.0.25114 or any unpatched version within the affected release line.
  2. Verify JavaScript execution settings
    In Foxit PhantomPDF, go to File > Preferences > JavaScript. Check if JavaScript is enabled for Adobe JavaScript APIs.
    Affected if JavaScript execution is enabled in the application settings.
  3. Confirm listbox form field usage
    Review any PDF forms in use that contain listbox fields with associated Keystroke actions. Open the PDF in PhantomPDF, select the listbox field, right-click, and check Properties > Keystroke tab.
    Affected if The environment contains PDF documents with listbox fields that have active Keystroke action scripts.
  4. Check for recent PDF files from untrusted sources
    Search for recently opened or downloaded PDF files, particularly from email attachments or unknown sources. Inspect file metadata and origin.
    Affected if Users have opened PDF files from untrusted or unknown sources recently.

A user is affected if they have Foxit PhantomPDF version 9.6.0.25114 installed with JavaScript enabled and have opened or could open malicious PDFs containing crafted listbox Keystroke actions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch/update to Foxit PhantomPDF to the latest version. Until patched, warn users not to open PDF files from untrusted sources and consider disabling JavaScript execution in PDF settings.

Fix this in Phantompdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17142 — 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-2019-17142 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