3dApplication · Foxitsoftware

CVE-2021-31466

HIGH · 7.8 CVSS v3.1 Published 2021-05-07
Fix available
A fix is available. Upgrade to after 10.1.3.37598 or later.
See remediation →
81/100
Remediation priority · High
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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit Reader 10.1.3.37598. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of U3D objects in PDF files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-13583.

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 Foxit Reader's handling of U3D (Universal 3D) objects embedded in PDF files. The lack of proper validation of user-supplied data allows reading past the end of an allocated data structure, which can be leveraged for arbitrary code execution in the context of the current process. User interaction required (opening malicious PDF).

MitigationUpdate Foxit Reader to the latest version; avoid opening untrusted PDF files or disable U3D content rendering in Reader settings until patched.

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
3dApplication
Affected:<= 9.7.4.29600>= 10.0.0.0, <= 10.1.3.37598

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
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Confirm Foxit Reader installation
    Check for Foxit Reader in installed programs (Control Panel > Programs and Features) or run: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\FoxitReader' /v DisplayName
    Affected if Foxit Reader is installed and version falls within <= 9.7.4.29600 or >= 10.0.0.0 and <= 10.1.3.37598
  2. Identify installed Foxit Reader version
    Run: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\FoxitReader' /v DisplayVersion (or check Help > About in the application)
    Affected if Version number is 9.7.4.29600 or lower, OR between 10.0.0.0 and 10.1.3.37598 inclusive
  3. Determine if 3D/U3D content rendering is enabled
    In Foxit Reader, go to File > Preferences > 3D and check if 'Enable 3D content' or similar U3D rendering option is checked/enabled
    Affected if U3D/3D content rendering is enabled in Reader preferences (the vulnerability only triggers when this feature processes a malicious PDF)
  4. Inspect PDF files for embedded U3D objects (optional)
    Use a PDF analysis tool or open the PDF in a hex editor and search for the string 'U3D' or look for 3D object streams
    Affected if U3D objects are present in PDF files opened by the user (required for exploitation)

You are affected if Foxit Reader version is 9.7.4.29600 or lower, or between 10.0.0.0 and 10.1.3.37598, AND U3D/3D content rendering is enabled, AND you open a PDF containing a malicious U3D object.

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
Upgrade available Upgrade to a release after 10.1.3.37598
Interim mitigation

Update Foxit Reader to the latest version; avoid opening untrusted PDF files or disable U3D content rendering in Reader settings until patched.

Fix this in 3d Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31466 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-31466 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