CVE-2019-6985
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 Read in Indexing or a Heap Overflow and crash during handling of certain PDF files that embed specifically crafted 3D content, due to an array access violation.
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 with the 3D Plugin Beta before 9.4.0.16807 suffer from an Out-of-Bounds Read during indexing operations and a Heap Overflow vulnerability. The vulnerability stems from array access violations when the application processes PDF files containing specially crafted 3D content, leading to potential memory corruption and arbitrary 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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Foxit product installationLocate Foxit Reader or PhantomPDF installation directory, typically in Program Files or Program Files (x86), or check the application's executable file propertiesAffected if Foxit Reader or PhantomPDF is found on the system
-
Identify installed versionRight-click the Foxit executable (e.g., FoxitReader.exe or PhantomPDF.exe), select Properties, and view the File Version field under the Details tabAffected if Version number is earlier than 9.4.0.16807
-
Locate and inspect 3D Plugin componentSearch for the 3D Plugin file within the Foxit installation directory, commonly named with '3d' in the filename or within a plugins folderAffected if 3D Plugin Beta version exists and is earlier than 9.4.0.16807
-
Verify 3D Plugin is loadedOpen Foxit Reader or PhantomPDF, go to Help > About Foxit Reader (or PhantomPDF), or check the plugins/modules list to see if the 3D Plugin is actively loadedAffected if The 3D Plugin is enabled and listed as active in the application
User is affected if Foxit Reader or PhantomPDF with the 3D Plugin Beta is installed and its version is earlier than 9.4.0.16807, with the 3D Plugin enabled.
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
Update Foxit Reader and PhantomPDF to version 9.4.0.16807 or later which includes the patched 3D Plugin. If 3D functionality is not required, the 3D Plugin can be disabled or removed to reduce attack surface.
- 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-6985 — 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-6985 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