dbcve.org
Foxit ReaderApplication · Foxitsoftware

CVE-2018-19347

HIGH · 7.1 CVSS v3.0 Published 2018-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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 · unedited
The 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 "Data from Faulting Address controls Branch Selection starting at U3DBrowser!PlugInMain+0x00000000000d11bb" 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 confidence

Out-of-bounds read vulnerability in the U3D (Universal 3D) plugin (U3DBrowser.fpi) of Foxit Reader allows remote attackers to cause denial of service or obtain sensitive information via a specially crafted U3D sample. The 'Data from Faulting Address controls Branch Selection' indicates memory contents from an out-of-bounds address can influence program execution flow, making it potentially exploitable for information disclosure beyond simple DoS.

MitigationUpdate Foxit Reader to a patched version that addresses this vulnerability; if immediate patching is not possible, consider disabling the U3D plugin or exercising caution with untrusted PDF files containing U3D content.

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
Foxit ReaderApplication
Affected:= 9.3.0.10826
U3dApplication
Affected:= 9.3.0.10809

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Foxit Reader installation and version
    Open Foxit Reader, then go to Help > About Foxit Reader to display the exact version number. Alternatively, check the application executable properties or use the application's version information dialog.
    Affected if The displayed version equals 9.3.0.10826 or falls within the affected version range.
  2. Locate and verify the U3D plugin file
    Find the U3DBrowser.fpi plugin file in the Foxit Reader installation directory (typically under a Plugins or Common folder). Right-click the file and view its Properties > Details to obtain its version information.
    Affected if The U3D plugin version equals 9.3.0.10809, matching the affected U3d version.
  3. Confirm U3D plugin is enabled
    In Foxit Reader, navigate to File > Preferences > Plugins. Verify whether the U3D plugin (U3DBrowser) is listed as enabled or loaded. Alternatively, check if the plugin appears in the application's plugin management interface.
    Affected if The U3D plugin is enabled or loaded in Foxit Reader.
  4. Check for U3D content processing capability
    Attempt to open a PDF containing 3D content or verify if the application has active support for rendering U3D/3D objects. This can be observed when opening PDFs with embedded 3D models, which trigger the U3D plugin.
    Affected if Foxit Reader can process or render U3D/3D content within PDF files, indicating the vulnerable code path is accessible.

A user is affected if Foxit Reader version 9.3.0.10826 or the U3D plugin version 9.3.0.10809 is installed and the U3D plugin is enabled and capable of processing U3D content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Foxit Reader to a patched version that addresses this vulnerability; if immediate patching is not possible, consider disabling the U3D plugin or exercising caution with untrusted PDF files containing U3D content.

Fix this in Foxit Reader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19347 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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