CVE-2022-43640
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 PDF files. Crafted data in a PDF file can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-18629.
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 · moderate confidenceOut-of-bounds read vulnerability in Foxit PDF Reader 12.0.1.12430 during PDF file parsing. The vulnerability allows reading past the end of an allocated buffer, enabling sensitive information disclosure. While the CVSS is 5.5, the vendor notes it can be chained with other vulnerabilities for arbitrary code execution.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Confirm Foxit PDF Reader installation and versionOpen Foxit PDF Reader, go to Help > About Foxit Reader, or right-click the application and select Properties to view the version number. Alternatively, check Add or Remove Programs (Windows) or the Applications folder (macOS) for the installed version.Affected if The installed version is earlier than 12.0.2 (for example, 12.0.1.12430 or any 11.x.x version)
-
Confirm Foxit PDF Editor installation and versionOpen Foxit PDF Editor, go to Help > About Foxit PDF Editor, or check the application's properties or Add/Remove Programs to locate the version number.Affected if The installed version is earlier than 10.1.10; OR between 11.0.0 and 11.2.4 (excluding 11.2.4); OR between 12.0.0.12394 and 12.0.2 (excluding 12.0.2)
-
Identify all Foxit applications on the systemSearch the system for any Foxit-related executables (FoxitReader.exe, FoxitEditor.exe, FoxitPhantomPDF.exe) using File Explorer or the command 'dir /s /b C:\*.exe | findstr -i Foxit' on Windows, or check the /Applications folder on macOS.Affected if Any Foxit PDF Reader version below 12.0.2 or Foxit PDF Editor version in the affected ranges listed above is found
You are affected if any Foxit PDF Reader version is below 12.0.2, or any Foxit PDF Editor version is below 10.1.10, between 11.0.0 and 11.2.4, or between 12.0.0.12394 and 12.0.2.
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 patched version. Until then, exercise caution with PDF files from untrusted sources and disable JavaScript execution in the PDF reader settings.
Foxit Pdf Reader: 12.0.2+ | Foxit Pdf Editor: 10.1.10+, 11.2.4+, or 12.0.2+
- 1. Determine which Foxit product is installed (Pdf Reader or Pdf Editor) and note the current version number
- 2. For Foxit Pdf Reader: upgrade to version 12.0.2 or later
- 3. For Foxit Pdf Editor: upgrade to version 10.1.10 or later (if on 10.x branch), OR version 11.2.4 or later (if on 11.x branch), OR version 12.0.2 or later (if on 12.x branch)
- 4. Download the appropriate fixed version from the official Foxit website (www.foxit.com)
- 5. Close any running instances of Foxit PDF Reader/Editor
- 6. Install the upgraded version following the on-screen instructions
- 7. Restart the application and verify the version number reflects the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43640 — 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-43640 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