CVE-2018-19341
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 FoxitReader!std::basic_ostream >::operator<<+0x0000000000087906" 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 confidenceAn out-of-bounds read vulnerability exists in the U3D (Universal 3D) plugin (version 9.3.0.10809) of Foxit Reader 9.3.0.10826. When processing a specially crafted U3D sample file, the application experiences a read access violation near NULL at the std::basic_ostream operator, allowing remote attackers to potentially cause denial of service or read sensitive information from memory.
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 if Foxit Reader is installed by looking for the application in Program Files (typically C:\Program Files\Foxit Software\Foxit Reader\) or by running 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Foxit*"}' in PowerShellAffected if Foxit Reader is installed on the system
-
Check Foxit Reader versionOpen Foxit Reader, go to Help > About Foxit Reader, or check the executable version by right-clicking foxitreader.exe and selecting Properties > Details. The Product Version should be 9.3.0.10826.Affected if The installed Foxit Reader version is exactly 9.3.0.10826
-
Locate and identify the U3D pluginNavigate to the Foxit Reader installation folder (typically C:\Program Files\Foxit Software\Foxit Reader\plugins\) and look for a file named u3d.dll or similar U3D-related plugin file.Affected if The U3D plugin file exists in the plugins directory
-
Check U3D plugin versionRight-click the U3D plugin file (such as u3d.dll) in the plugins folder, select Properties > Details to view the File Version or Product Version. This should be 9.3.0.10809.Affected if The U3D plugin version is exactly 9.3.0.10809
You are affected if Foxit Reader version 9.3.0.10826 with U3D plugin version 9.3.0.10809 is installed and the U3D plugin is present and 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 dataUpdate Foxit Reader to a version that patches this vulnerability, or disable/remove the U3D plugin if 3D rendering functionality is not required.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19341 — 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-19341 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