dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-42369

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-18344.

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 (Universal 3D) file parser allows remote attackers to read beyond the boundaries of an allocated buffer by crafting malicious U3D data embedded in PDF files. This information disclosure can be chained with other vulnerabilities to achieve arbitrary code execution in the current process context.

MitigationAvoid opening PDF files containing U3D content from untrusted sources. Apply vendor patches when available. Consider disabling U3D/3D content rendering in PDF readers as a defense-in-depth measure.

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. Check installed PDF-XChange Editor version
    Open the application, go to Help > About PDF-XChange Editor, or check the version displayed on the application's title bar. Alternatively, right-click the application shortcut and select Properties to view the version in the Details tab.
    Affected if The version number displayed is less than 9.5.366.0
  2. Check if U3D/3D content rendering is enabled in application preferences
    Open PDF-XChange Editor and navigate to Edit > Preferences > 3D/Multimedia (or similar path depending on version). Look for settings related to 'Enable 3D content', 'Render U3D objects', or '3D view' options.
    Affected if 3D/U3D rendering is enabled (the checkbox is checked/selected)
  3. Identify PDFs with embedded U3D content
    Use the application's built-in analysis or open the PDF and check the navigation pane for 'U3D' or '3D' objects listed under the Models or 3D nodes in the document structure.
    Affected if The PDF file contains embedded U3D data and the application is configured to render it

A user is affected if they have PDF-XChange Editor version below 9.5.366.0, have 3D/U3D rendering enabled, and open a PDF containing malicious 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 PDF files containing U3D content from untrusted sources. Apply vendor patches when available. Consider disabling U3D/3D content rendering in PDF readers as a defense-in-depth measure.

Recommended fix High confidence

PDF-XChange Editor 9.5.366.0 or later

  1. Navigate to the official PDF-XChange Editor download page at www.tracker-software.com
  2. Download the latest version of PDF-XChange Editor (version 9.5.366.0 or later)
  3. Close any running instances of PDF-XChange Editor
  4. Install the downloaded update by running the installer
  5. Restart PDF-XChange Editor after installation completes
  6. Verify the installed version is 9.5.366.0 or higher via Help > About
Caveat Routine security update; no significant breaking changes expected for typical users

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-42369 — 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-42369 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