CVE-2022-37375
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 PDF-XChange Editor. 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 JPC files. Crafted data in a JPC 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-18069.
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 confidenceThis is an out-of-bounds read vulnerability in PDF-XChange Editor's JPC (JPEG 2000 codestream) file parser. Crafted JPC files with malformed data can cause the application to read past the end of an allocated buffer, potentially exposing sensitive memory contents. While primarily an information disclosure issue, it can be chained with other vulnerabilities to achieve 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= 9.3.361.0CVSS 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 PDF-XChange Editor installationCheck for PDF-XChange Editor in installed programs via Control Panel > Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'PDF-XChange Editor'Affected if PDF-XChange Editor is found on the system
-
Identify installed version numberRight-click the PDF-XChange Editor application shortcut or executable, select Properties, and check the Details tab for the Product Version field; alternatively, look for the version in the uninstall registry entry found in the previous stepAffected if Version displayed is 9.3.361.0 exactly
-
Verify JPC file handling capability existsAttempt to open a benign JPC/JPEG 2000 file in PDF-XChange Editor, or check if the application lists JPC or JPEG 2000 support in its supported file formats documentation or About dialogAffected if JPC file parsing functionality is present and operational
-
Check for recent file association activityReview recently opened files in PDF-XChange Editor, or examine Windows prefetch/temp folders for .jpc file access, or check the application's recent documents listAffected if JPC files have been opened in the application
A system is affected if PDF-XChange Editor version 9.3.361.0 is installed and the JPC file parsing feature is enabled or has been used to open files.
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.
From vendor dataUsers should avoid opening untrusted JPC files or visiting malicious pages until a vendor patch is released. Consider disabling JPC file handling or using application isolation as a temporary workaround.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37375 — 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-37375 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