CVE-2019-6982
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 · uneditedAn issue was discovered in Foxit 3D Plugin Beta before 9.4.0.16807 for Foxit Reader and PhantomPDF. The application could encounter an Out-of-Bounds Write and crash during the handling of certain PDF files that embed specifically crafted 3D content, because of the improper handling of a logic exception in the IFXASSERT function.
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 confidenceFoxit Reader and PhantomPDF's 3D Plugin contains an out-of-bounds write vulnerability triggered by opening PDF files with specially crafted 3D content. The vulnerability stems from improper exception handling in the IFXASSERT function, allowing memory corruption that leads to 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< 9.4.0.16807CVSS 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.0/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 Foxit installation and versionCheck the installed version of Foxit Reader or PhantomPDF by reviewing the program's properties in the executable (typically located in Program Files\Foxit Software\Foxit Reader or Program Files\Foxit Software\PhantomPDF) or by querying the Windows Registry under HKLM\SOFTWARE\Foxit Software for the Version keyAffected if The installed version is lower than 9.4.0.16807
-
Locate the 3D plugin componentVerify the presence of the 3D plugin DLL module (commonly named 3d.dll or within a plugins folder under the Foxit installation directory) which handles 3D content rendering in PDF filesAffected if The 3D plugin DLL exists in the Foxit installation directory
-
Confirm plugin is enabledCheck if the 3D plugin is loaded and active by examining Foxit's plugin settings (accessible via File > Preferences > Plugins in the application) or by inspecting which modules are loaded when Foxit runsAffected if The 3D plugin is enabled or loads automatically when opening PDF files with 3D content
-
Cross-reference version with affected rangeCompare the identified Foxit version number against the affected range of versions prior to 9.4.0.16807Affected if The installed version falls below 9.4.0.16807 AND the 3D plugin component is present and enabled
A user is affected if Foxit Reader or PhantomPDF version is below 9.4.0.16807 and the 3D plugin module is installed and enabled for handling PDF 3D content.
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.4.0.16807
Users must update Foxit Reader and PhantomPDF to version 9.4.0.16807 or later to remediate this vulnerability. Organizations should inventory affected Foxit installations and deploy the update via standard software distribution mechanisms.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6982 — 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-2019-6982 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