CVE-2018-10302
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 · uneditedA use-after-free in Foxit Reader before 9.1 and PhantomPDF before 9.1 allows remote attackers to execute arbitrary code, aka iDefense ID V-jyb51g3mv9.
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 use-after-free vulnerability in Foxit Reader before version 9.1 and PhantomPDF before version 9.1 allows remote attackers to execute arbitrary code via specially crafted PDF files. The vulnerability involves improper memory management where freed memory is accessed after being deallocated, leading to potential code execution.
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< 9.1< 9.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.0/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.
-
Check Foxit Reader versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Foxit Software\Foxit Reader\ or HKCU\SOFTWARE\Foxit Software\Foxit Reader\ and locate the Version key. Alternatively, right-click on Foxit Reader.exe in the installation directory (typically C:\Program Files\Foxit Software\Foxit Reader\ or C:\Program Files (x86)\Foxit Software\Foxit Reader\) and view the Details tab for Product Version.Affected if The version listed is lower than 9.1.0.0 or the registry key does not exist but Foxit Reader is installed.
-
Check PhantomPDF versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Foxit Software\PhantomPDF\ or HKCU\SOFTWARE\Foxit Software\PhantomPDF\ and locate the Version key. Alternatively, right-click on PhantomPDF.exe in the installation directory (typically C:\Program Files\Foxit Software\PhantomPDF\) and view the Details tab for Product Version.Affected if The version listed is lower than 9.1.0.0 or the registry key does not exist but PhantomPDF is installed.
-
Identify all Foxit applications installedOpen Programs and Features in Control Panel or use PowerShell command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.Publisher -like '*Foxit*'} | Select-Object DisplayName, DisplayVersionAffected if Any Foxit Reader or PhantomPDF entry shows a version below 9.1.
If either Foxit Reader or PhantomPDF is installed with a version number less than 9.1, the environment is vulnerable to this use-after-free flaw when opening specially crafted PDF files.
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.
From vendor data9.1
Upgrade Foxit Reader and PhantomPDF to version 9.1 or later. Until then, avoid opening untrusted PDF files and disable JavaScript execution in the application settings.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10302 — 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-2018-10302 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