CVE-2022-42391 json
This vulnerability allows remote attackers to disclose sensitive information on affected installations of PDF-XChange Editor.
published 3y ago modified 4mo ago also EUVD-2022-45465
- cvss
- 3.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
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-18660.
Patch / fix
- pdf-xchange pdf-xchange_editor 9.5.366.0
Is CVE-2022-42391 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected products
- PDF-XChange PDF-XChange Editor
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
tracker-software.com
/product/pdf-xchange-editor/history
vendor-advisory
-
zerodayinitiative.com
/advisories/ZDI-22-1382/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-42391
- NVD CVE-2022-42391
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.