dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-42383

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

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

Out-of-bounds read vulnerability in PDF-XChange Editor's U3D (3D PDF) file parser. Crafted U3D data triggers a read past the end of an allocated buffer, allowing remote information disclosure. While this is primarily an information disclosure issue, the advisory notes it can be chained with other vulnerabilities for arbitrary code execution.

MitigationUpdate PDF-XChange Editor to the vendor-provided patch. Until patched, avoid opening U3D files or 3D PDF content from untrusted sources.

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 for the application in Program Files (typically C:\Program Files\PDF-XChange Editor or C:\Program Files (x86)\PDFXEdit), or search for PDFXEdit.exe in the system
    Affected if The application is present on the system
  2. Identify the installed version number
    Right-click on PDFXEdit.exe, select Properties, then view the Details tab for the Product Version field. Alternatively, open PDF-XChange Editor, go to Help > About to view the version
    Affected if The version is displayed as less than 9.5.366.0
  3. Verify the U3D parser component is present
    Confirm the PDF-XChange Editor installation includes the full feature set - the U3D (3D PDF) parser is a built-in component of the Editor and cannot be selectively disabled
    Affected if The application has full 3D PDF rendering capabilities enabled (this is the default state)
  4. Determine if 3D PDF content has been processed
    Check recent PDF files opened with the application, particularly files containing 3D models or U3D content. The vulnerability triggers when opening a crafted U3D file
    Affected if The user has opened or may open U3D files from untrusted sources

A system is affected if PDF-XChange Editor is installed with a version lower than 9.5.366.0 and the user processes U3D/3D PDF content, since the out-of-bounds read occurs in the U3D parser when opening a specially crafted file.

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

Update PDF-XChange Editor to the vendor-provided patch. Until patched, avoid opening U3D files or 3D PDF content from untrusted sources.

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) to download the latest version
  2. Ensure the downloaded version is 9.5.366.0 or later
  3. Install the updated version of PDF-XChange Editor
  4. Verify the installed version matches or exceeds 9.5.366.0 by checking Help > About in the application

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

Fix this in Pdf Xchange Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42383 — 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-42383 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