PhantompdfApplication · Foxitsoftware

CVE-2018-17639

HIGH · 8.8 CVSS v3.0 Published 2019-01-24
Fix available
A fix is available. Upgrade to after 9.2.0.9297 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
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader 9.2.0.9297. 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 handling of the setElement method. 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-6475.

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

This is a use-after-free type vulnerability in Foxit Reader 9.2.0.9297 where the setElement method fails to validate object existence before performing operations on it. An attacker can exploit this by crafting a malicious PDF file that, when opened by a victim, allows arbitrary code execution in the context of the current process. User interaction is required (opening a malicious file or visiting a malicious page).

MitigationApply the vendor patch for Foxit Reader to the latest version and exercise caution when opening PDF files from untrusted sources, as user interaction is required for exploitation.

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.2.0.9297
ReaderApplication
Affected:<= 9.2.0.9297

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.0/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 if Foxit Reader is installed
    Navigate to C:\Program Files\Foxit Software\Foxit Reader\ or C:\Program Files (x86)\Foxit Software\Foxit Reader\ and verify the folder exists, or check Add/Remove Programs for Foxit Reader entry
    Affected if Foxit Reader is found installed on the system
  2. Find installed Foxit Reader version
    Right-click on Foxit Reader.exe in the installation folder, select Properties, then go to the Details tab and note the Product Version field
    Affected if The version shown is 9.2.0.9297 or lower
  3. Check if PhantomPDF is installed
    Navigate to C:\Program Files\Foxit Software\PhantomPDF\ or C:\Program Files (x86)\Foxit Software\PhantomPDF\ and verify the folder exists, or check Add/Remove Programs for PhantomPDF entry
    Affected if PhantomPDF is found installed on the system
  4. Find installed PhantomPDF version
    Right-click on PhantomPDF.exe in the installation folder, select Properties, then go to the Details tab and note the Product Version field
    Affected if The version shown is 9.2.0.9297 or lower
  5. Compare version to affected range
    If either product is installed, verify that the exact version number is less than or equal to 9.2.0.9297 using the version from the Details tab
    Affected if The installed version of Foxit Reader or PhantomPDF is 9.2.0.9297 or any version lower than 9.2.0.9297

If Foxit Reader or PhantomPDF is installed with a version at or below 9.2.0.9297, the environment is affected by this CVE.

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 9.2.0.9297
Interim mitigation

Apply the vendor patch for Foxit Reader to the latest version and exercise caution when opening PDF files from untrusted sources, as user interaction is required for exploitation.

Fix this in Phantompdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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