CVE-2022-37380
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.1.53537. 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 ADBC objects. 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-17169.
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 confidenceThis is an out-of-bounds read vulnerability in Foxit PDF Reader's handling of ADBC (Adobe Database Connectivity) objects. By triggering specific JavaScript actions, an attacker can read past the end of an allocated buffer, leading to sensitive information disclosure. While the primary impact is information disclosure, this vulnerability can be chained with other flaws 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.
-
Confirm Foxit PDF Reader is installedOpen Foxit PDF Reader and go to Help > About Foxit Reader, or check Programs and Features in Control Panel for Foxit PDF Reader entryAffected if Foxit PDF Reader is present on the system
-
Identify installed versionIn Foxit PDF Reader, navigate to Help > About Foxit Reader and note the full version number displayedAffected if The version shown is less than 12.0.1 (for example, 12.0.0.x where x is less than 1, or any version 11.x.x or earlier)
-
Verify JavaScript is enabledIn Foxit PDF Reader, go to File > Preferences > JavaScript and confirm the 'Enable JavaScript' option is checkedAffected if JavaScript is enabled - this is required for the vulnerability to be triggered
-
Check for ADBC plugin presenceIn Foxit PDF Reader, go to File > Preferences > General > Plugins and look for ADBC (Adobe Database Connectivity) related plugin or componentAffected if ADBC plugin or database connectivity feature is installed and available
A user is affected if Foxit PDF Reader version is below 12.0.1 and JavaScript is enabled, allowing the out-of-bounds read via ADBC object handling to be triggered.
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 as soon as a vendor patch is available, and avoid opening untrusted PDF files or visiting malicious pages until the update is applied.
Pdf Editor: 10.1.9, 11.2.3, or 12.0.1+ | Pdf Reader: 12.0.1+
- Identify whether Foxit Pdf Editor or Foxit Pdf Reader is installed by checking the application name in the Start menu or Add/Remove Programs
- Check the current version of the installed Foxit application (Help > About in the application menu)
- If using Pdf Editor with version < 10.1.9, upgrade to version 10.1.9 or later
- If using Pdf Editor with version >= 11.0.0 and < 11.2.3, upgrade to version 11.2.3 or later
- If using Pdf Editor version 12.0.0.12394, upgrade to version 12.0.1 or later
- If using Pdf Reader with version < 12.0.1, upgrade to version 12.0.1 or later
- Download the fixed version from the official Foxit website at www.foxit.com
- Run the installer and follow the prompts to complete the upgrade
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-37380 — 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-37380 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