dbcve.org
Pdf ToolsApplication · Pdf Xchange

CVE-2024-27324

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-01
Fix available
A fix is available. Upgrade to 10.1.3.383 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
PDF-XChange Editor TIF File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. 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 TIF files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-22270.

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 · moderate confidence

PDF-XChange Editor contains an out-of-bounds read vulnerability in its TIF file parser due to insufficient validation of user-supplied data. The flaw allows reading past the end of an allocated buffer, exposing sensitive information from memory. While the primary impact is information disclosure, the advisory notes this can be chained with other vulnerabilities to achieve code execution.

MitigationAvoid opening untrusted TIF files or visiting malicious pages until the vendor releases a patch. Apply vendor security updates promptly once available.

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 ToolsApplication
Affected:>= 10.1.1.381, < 10.1.3.383
Pdf Xchange EditorApplication
Affected:>= 10.1.1.381, < 10.1.3.383

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 if PDF-XChange Editor is installed
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*PDF-XChange*'} | Select-Object DisplayName, DisplayVersion
    Affected if No PDF-XChange product is found in the installed programs list, the user is not affected by this CVE.
  2. Identify the exact installed version
    Launch PDF-XChange Editor, go to Help > About, or right-click the application in Programs and Features to view the version number. Note the full version string including build number (e.g., 10.1.2.381)
    Affected if The displayed version cannot be determined or is not visible, further investigation may be needed.
  3. Compare version against affected range
    The affected range is versions >= 10.1.1.381 and < 10.1.3.383. Compare your installed build number (the three-digit number after the minor version, such as 381 in 10.1.1.381) against this range
    Affected if Your installed version falls within >= 10.1.1.381 and < 10.1.3.383, meaning your installation is affected by this vulnerability.
  4. Confirm TIF file handling is in use
    The vulnerability exists in the TIF file parser component. Check if the application has processed or can process TIF files by examining recent file associations or looking for TIF-related features in the application's import options
    Affected if TIF file parsing is enabled and the application processes TIF images, the vulnerable code path can be triggered.

If PDF-XChange Editor or Pdf Xchange Pdf Tools is installed with a version between 10.1.1.381 and 10.1.2.x (inclusive) and TIF file handling is used, the environment is affected by CVE-2024-27324.

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 10.1.3.383 or later
Fixed in 10.1.3.383
Interim mitigation

Avoid opening untrusted TIF files or visiting malicious pages until the vendor releases a patch. Apply vendor security updates promptly once available.

Recommended fix High confidence

PDF-XChange Editor/PDF Tools version 10.1.3.383 or later

  1. 1. Verify the current version of PDF-XChange Editor or PDF Tools installed on the system
  2. 2. Navigate to the official PDF-XChange website or trusted download source to obtain version 10.1.3.383 or later
  3. 3. Download the installer for the fixed version
  4. 4. Close any running instances of PDF-XChange Editor or PDF Tools
  5. 5. Install the updated version, ensuring to follow standard installation procedures
  6. 6. Verify the installation was successful and the version has been updated

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

Fix this in Pdf Tools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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