CVE-2022-43641
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 · uneditedThis vulnerability allows remote attackers to disclose sensitive information on affected installations of Foxit PDF Reader 12.0.1.12430. 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 parsing of U3D files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-18894.
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 confidenceA use-after-free or null pointer dereference vulnerability exists in Foxit PDF Reader's U3D file parser. The code fails to validate the existence of an object before performing operations on it, leading to sensitive information disclosure. When chained with other vulnerabilities, this can enable arbitrary code execution in the context of the current process.
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< 10.1.10>= 11.0.0, < 11.2.4>= 12.0.0.12394, < 12.0.2< 12.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Foxit PDF Reader is installedLook for Foxit Software folder in Program Files (x86) or Program Files, or check Add/Remove Programs for Foxit entriesAffected if Foxit PDF Reader or Foxit PDF Editor is installed on the system
-
Locate the Foxit executable to check versionFind foxitreader.exe or foxitpdfeditor.exe in the Foxit Software installation directory (typically C:\Program Files (x86)\Foxit Software\ or C:\Program Files\Foxit Software\)Affected if Foxit executable is found on the system
-
Determine the installed version numberRight-click the Foxit executable, select Properties, go to the Details tab, and note the Product Version; or check the version shown in Add/Remove ProgramsAffected if Unable to retrieve version information from the Foxit installation
-
Compare version against affected rangesMatch the installed version to these vulnerable ranges: Reader/Editor versions below 10.1.10, versions 11.0.0 through 11.2.3, or versions 12.0.0.12394 through 12.0.1; note that version 12.0.2 and later are not affectedAffected if Installed version is below 10.1.10, between 11.0.0 and 11.2.3 inclusive, or between 12.0.0.12394 and 12.0.1 inclusive
The system is affected if Foxit PDF Reader is installed at any version below 12.0.2, or Foxit PDF Editor is installed at versions below 10.1.10, between 11.0.0-11.2.3, or between 12.0.0.12394-12.0.1.
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.
dbcve · scoped10.1.1011.2.412.0.2
Update Foxit PDF Reader to the latest version; avoid opening untrusted PDF files from unknown sources and disable automatic opening of files in the reader settings.
Foxit Pdf Reader 12.0.2+ or Foxit Pdf Editor 10.1.10 / 11.2.4 / 12.0.2+
- 1. Identify the Foxit product installed (Pdf Editor or Pdf Reader)
- 2. Check current version by going to Help > About in Foxit application
- 3. For Foxit Pdf Reader: upgrade to version 12.0.2 or later from the official Foxit website
- 4. For Foxit Pdf Editor: upgrade to version 10.1.10 (for legacy users), 11.2.4 (for version 11.x users), or 12.0.2 (for version 12.x users) from the official Foxit website
- 5. Verify the upgrade was successful by checking Help > About shows the fixed version
- 6. Ensure U3D file parsing is not automatically enabled if presented with untrusted PDF files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43641 — 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-2022-43641 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