dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-42375

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 9.5.366.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
This 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 U3D files. Crafted data in a U3D 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-18404.

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 confidence

An out-of-bounds read vulnerability in PDF-XChange Editor's U3D file parser allows attackers to read past the end of an allocated buffer by crafting malicious U3D data. While primarily an information disclosure issue (CVSS 5.5), the advisory notes this can be chained with other vulnerabilities for arbitrary code execution.

MitigationAvoid opening U3D files from untrusted sources and maintain up-to-date versions of PDF-XChange Editor. Consider disabling U3D rendering if not required.

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
Pdf Xchange EditorApplication
Affected:< 9.5.366.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PDF-XChange Editor is installed
    Check installed programs on the system for PDF-XChange Editor or PDF-XChange Editor Plus. On Windows, this can be done via Control Panel > Programs and Features, or by searching for the application in the Start menu.
    Affected if The application is present on the system
  2. Identify the installed version
    Open PDF-XChange Editor, then navigate to Help > About PDF-XChange Editor (or use the keyboard shortcut typically found in the Help menu). The version number will be displayed in the About dialog.
    Affected if The version number displayed is lower than 9.5.366.0 (for example, 9.5.365.0, 9.4.x.x, or earlier versions)
  3. Verify U3D rendering is accessible
    Check whether the application can open or render U3D (Universal 3D) content within PDF files. This is typically a built-in parser feature that activates when opening a PDF containing U3D objects, not a separate setting that can be toggled on/off through normal user preferences.
    Affected if The application supports opening PDF files containing U3D content, which is the default behavior for this product

A user is affected if PDF-XChange Editor is installed with a version lower than 9.5.366.0 and the application is capable of processing U3D files, which occurs simply by opening a maliciously crafted PDF containing U3D data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.5.366.0 or later
Fixed in 9.5.366.0
Interim mitigation

Avoid opening U3D files from untrusted sources and maintain up-to-date versions of PDF-XChange Editor. Consider disabling U3D rendering if not required.

Recommended fix High confidence

PDF-XChange Editor 9.5.366.0 or later

  1. Navigate to the official PDF-XChange Editor website (www.tracker-software.com) using a web browser
  2. Locate and download version 9.5.366.0 or later of PDF-XChange Editor
  3. Close any running instances of PDF-XChange Editor
  4. Uninstall the current vulnerable version through Windows Control Panel > Programs and Features
  5. Run the installer for the downloaded fixed version (9.5.366.0 or later)
  6. Follow the installation wizard prompts to complete the installation
  7. Restart the application and verify the version number matches the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Xchange Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42375 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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