dbcve.org
Power PdfApplication · Tungstenautomation

CVE-2023-51610

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 5.0.0.21 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
Kofax Power PDF JP2 File Parsing Use-After-Free Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Kofax Power PDF. 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 JP2 files. The issue results from the lack of validating the existence of an object prior to performing operations on the 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-21835.

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

This is a Use-After-Free vulnerability in Kofax Power PDF's JP2 file parsing component. The flaw results from the lack of validating object existence prior to performing operations on it, allowing remote attackers to potentially disclose sensitive information or, when chained with other vulnerabilities, execute arbitrary code in the current process context.

MitigationUsers should avoid opening untrusted or unknown JP2 files until vendor patches are applied. Organizations should deploy endpoint detection and network-based controls to block malicious file types and monitor for suspicious activity.

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
Power PdfApplication
Affected:< 5.0.0.21

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 Power PDF installation
    Check for the presence of Kofax Power PDF or Tungstenautomation Power PDF in installed programs (Windows: Programs and Features, or check C:\Program Files\Kofax or C:\Program Files\Tungstenautomation for the Power PDF directory)
    Affected if Kofax Power PDF or Tungstenautomation Power PDF is installed on the system
  2. Identify installed version
    Locate the Power PDF executable (typically in the installation folder, often named PowerPDF.exe or similar), right-click and select Properties, or run: wmic product where "name like '%%Power PDF%%'" get version
    Affected if The installed version is lower than 5.0.0.21 (e.g., 5.0.0.20, 4.x, 3.x versions)
  3. Verify JP2 parsing capability is present
    Check if the JP2 parsing module exists in the installation directory (look for files related to image/raster processing, commonly in a 'Bin' or 'Lib' subfolder within the Power PDF installation path)
    Affected if The JP2 parsing component is present in the installation
  4. Check for recent JP2 file activity
    Review Windows PowerShell Get-WinEvent logs for Event ID 4656 or check the application's recent files list (AppData\Roaming\Kofax\Power PDF\RecentFiles) for .jp2 file entries
    Affected if Users have recently opened JP2 files using Power PDF

A system is affected if Tungstenautomation or Kofax Power PDF is installed with a version lower than 5.0.0.21 and users process JP2 files with it.

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

Users should avoid opening untrusted or unknown JP2 files until vendor patches are applied. Organizations should deploy endpoint detection and network-based controls to block malicious file types and monitor for suspicious activity.

Recommended fix Moderate confidence

Kofax Power PDF 5.0.0.21 or later

  1. Identify the current version of Kofax Power PDF installed on the system
  2. Navigate to the official Kofax support or download page for Power PDF
  3. Download and install Power PDF version 5.0.0.21 or later
  4. Restart the application after installation
  5. Verify the installed version matches or exceeds 5.0.0.21
Caveat Review release notes for version 5.0.0.21 for any functional changes or migration requirements

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

Fix this in Power Pdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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