CVE-2018-19345
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 · uneditedThe u3d plugin 9.3.0.10809 (aka plugins\U3DBrowser.fpi) in FoxitReader.exe in Foxit Reader 9.3.0.10826 allows remote attackers to cause a denial of service (out-of-bounds read) or obtain sensitive information via a U3D sample because of a "Read Access Violation near NULL starting at U3DBrowser!PlugInMain+0x0000000000053f8b" issue.
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 confidenceOut-of-bounds read vulnerability in the U3D (Universal 3D) plugin (U3DBrowser.fpi) of Foxit Reader allows remote attackers to cause denial of service or potentially obtain sensitive information via a specially crafted U3D sample in PDF files. The issue manifests as a Read Access Violation near NULL in the PlugInMain function.
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.3.0.10826= 9.3.0.10809CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Verify Foxit Reader installationCheck for Foxit Reader in program files (C:\Program Files\Foxit Software\Foxit Reader\) or use registry key HKEY_LOCAL_MACHINE\SOFTWARE\Foxitsoftware\Foxit ReaderAffected if Foxit Reader is not installed, the CVE does not apply
-
Determine Foxit Reader versionRun 'Foxit Reader.exe -v' from command line or check version in Help > About Foxit Reader UI, or registry at HKEY_LOCAL_MACHINE\SOFTWARE\Foxitsoftware\Foxit Reader\AppVersionAffected if Version equals exactly 9.3.0.10826, which is the affected version
-
Locate U3D plugin fileSearch for U3DBrowser.fpi in the Foxit Reader installation folder, typically under plugins\u3d or similar path within the Foxit Reader directoryAffected if U3D plugin file exists and matches version 9.3.0.10809 (or if version cannot be determined but file is present)
-
Check if U3D plugin is enabledIn Foxit Reader, go to File > Preferences > Plugins > PDF/3D and verify if U3D plugin is loaded/enabled, or check for u3d plugin entry in registryAffected if U3D plugin is enabled and loaded by Foxit Reader
User is affected if Foxit Reader version 9.3.0.10826 is installed AND the U3D plugin (U3DBrowser.fpi) version 9.3.0.10809 is present and enabled, allowing specially crafted U3D content in PDF files to trigger the out-of-bounds read.
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 dataApply vendor-supplied patch from Foxit to update the u3d plugin, or disable the U3D plugin in Foxit Reader if 3D content is not required; avoid opening untrusted PDF files from unknown sources.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19345 — 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-19345 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