Security Resilience

CVE-2023-42076

Memory Safety in Pdf-Xchange Pdf-Tools 10.0.1.371

Published
03 May 2024
Modified
16 May 2025
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0048 42th percentile
Risk Priority 62 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-42076 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Pdf-Xchange Pdf-Tools. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

PDF-XChange Editor PDF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. User interaction is required to exploit this vulnerability in that the target must…

more

visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PDF files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-21762.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-39494Same product: Pdf-Xchange Pdf-Tools
CVE-2023-42083Same product: Pdf-Xchange Pdf-Tools
CVE-2023-39492Same product: Pdf-Xchange Pdf-Tools
CVE-2023-42077Same product: Pdf-Xchange Pdf-Tools
CVE-2023-42085Same product: Pdf-Xchange Pdf-Tools
CVE-2025-0903Same vendor: Pdf-Xchange
CVE-2025-6660Same product: Pdf-Xchange Pdf-Tools
CVE-2024-33505Shared CWE-122, CWE-787
CVE-2026-26108Shared CWE-122, CWE-787
CVE-2024-11608Shared CWE-122, CWE-787

Affected Assets

pdf-xchange
pdf-tools
10.0.1.371
pdf-xchange
pdf-xchange editor
10.0.1.371

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 full match
blocks

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
blocks

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance can detect heap overflows before release.

prevents

Training developers in secure coding practices (bounds checking, safe memory handling) reduces some out-of-bounds write instances, but the defect requires deep technical knowledge and even trained developers make these mistakes, so only a minority of instances are prevented.

prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

prevents

A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25-8.29), so a faithfully implemented clause reduces ordinary implementation-phase software weaknesses like heap-based buffer overflows in delivered code, but the effect is mediated by supplier practice and is bounded by the ceiling the owner has set on this clause for this verb.

finds

A.8.8's reach is DISCLOSURE — it surfaces heap-based buffer overflows only where they appear as published CVEs in third-party components in the inventory. CWE-122 is overwhelmingly an implementation-phase defect in custom code, which A.8.8 does not read; the disclosed third-party share is a minority, matching the same logic that graded A.8.8 -> CWE-89 at `partial`.

References