CVE-2022-37386
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 11.2.2.53575. 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 resetForm method. By performing actions in JavaScript, an attacker can trigger a read past the end of an allocated 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-17550.
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 resetForm method of Foxit PDF Reader 11.2.2.53575. By crafting malicious JavaScript within a PDF file, an attacker can trigger a read past the end of an allocated memory object, leading to sensitive information disclosure. This vulnerability can be chained with other vulnerabilities to achieve 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.9>= 11.0.0, < 11.2.3= 12.0.0.12394< 12.0.1CVSS 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.
-
Locate Foxit PDF Reader installationCheck the Windows Programs and Features (appwiz.cpl), or look in common installation paths such as C:\Program Files\Foxit Software\Foxit Reader or C:\Program Files (x86)\Foxit Software\Foxit Reader. The executable is typically FoxitReader.exe.Affected if Foxit PDF Reader is installed on the system
-
Identify installed Foxit PDF Reader versionRight-click on FoxitReader.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, run Foxit Reader, click Help > About Foxit Reader to display the version number.Affected if The version shown is < 12.0.1 (for Reader); for Editor, versions < 10.1.9, or >= 11.0.0 but < 11.2.3, or exactly 12.0.0.12394 are affected
-
Verify if JavaScript is enabled in Foxit settingsOpen Foxit Reader, go to File > Preferences > JavaScript. Check whether Enable Adobe JavaScript is checked. The vulnerability is triggered through malicious JavaScript embedded in a PDF file.Affected if JavaScript is enabled and the installed version falls within the affected ranges above
A user is affected if Foxit PDF Reader version is below 12.0.1 (or Foxit PDF Editor is in the affected Editor ranges) AND JavaScript is enabled in the Foxit preferences, allowing malicious PDF files to trigger the out-of-bounds read.
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.911.2.312.0.1
Update Foxit PDF Reader to the latest version with the security patch. Avoid opening PDF files from untrusted sources or visiting malicious web pages that could trigger the malicious JavaScript.
Pdf Reader: 12.0.1 or later | Pdf Editor: 10.1.9+, 11.2.3+, or version newer than 12.0.0.12394
- 1. Identify the installed Foxit product (Pdf Reader or Pdf Editor) and note the exact version number
- 2. Navigate to the official Foxit download page at www.foxit.com
- 3. Download the appropriate fixed version for your product: For Pdf Reader, download version 12.0.1 or later; For Pdf Editor, download version 10.1.9 or later, or version 11.2.3 or later, or a version newer than 12.0.0.12394
- 4. Close all Foxit applications before running the installer
- 5. Run the installer and follow the prompts to complete the upgrade
- 6. Verify the upgrade was successful by checking Help > About in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37386 — 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-37386 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