CVE-2022-37384
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 execute arbitrary code 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 delay method. 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 vulnerability to execute code in the context of the current process. Was ZDI-CAN-17327.
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 11.2.1.53537 within the delay method. The flaw allows remote code execution because the code fails to validate that an object exists before performing operations on it. An attacker can exploit this by tricking a user into opening a malicious PDF file.
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
- 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 PDF Reader in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or check for the executable at C:\Program Files\Foxit\FoxitReader.exe or C:\Program Files (x86)\Foxit\FoxitReader.exeAffected if Foxit PDF Reader is found on the system
-
Check if Foxit PDF Editor is installedLook for Foxit PDF Editor in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or check for the executable at C:\Program Files\Foxit\Foxit PDF Editor.exe or in similar Program Files directoriesAffected if Foxit PDF Editor is found on the system
-
Determine the installed version of Foxit PDF ReaderRight-click on FoxitReader.exe and select Properties > Details to view the File Version, or query the registry key HKLM\SOFTWARE\Foxit Software\Foxit PDF Reader for the Version valueAffected if The version displayed is less than 12.0.1
-
Determine the installed version of Foxit PDF EditorRight-click on Foxit PDF Editor.exe and select Properties > Details to view the File Version, or query the registry key HKLM\SOFTWARE\Foxit Software\Foxit PDF Editor for the Version valueAffected if The version displayed is less than 10.1.9, or is 11.0.0 through 11.2.2, or equals 12.0.0.12394
A user is affected if Foxit PDF Reader version less than 12.0.1 or Foxit PDF Editor version less than 10.1.9, between 11.0.0 and 11.2.2, or exactly 12.0.0.12394 is installed on their system.
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
Users should update to the latest version of Foxit PDF Reader to remediate this vulnerability. Avoid opening untrusted PDF files from unknown sources.
Pdf Reader: upgrade to >= 12.0.1 | Pdf Editor: upgrade to >= 10.1.9 (10.x branch), >= 11.2.3 (11.x branch), or >= 12.0.1 (12.x branch)
- 1. Identify the currently installed Foxit PDF Reader or Pdf Editor version by opening the application and navigating to Help > About Foxit PDF Reader/Editor
- 2. Download the appropriate fixed version from the official Foxit website (www.foxit.com) - do not download from third-party sources
- 3. Close all Foxit PDF Reader/Editor instances before installing the update
- 4. Run the downloaded installer and follow the prompts to complete the installation
- 5. After installation, verify the version by checking Help > About to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37384 — 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-37384 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