Power PdfApplication · Tungstenautomation

CVE-2023-37334

HIGH · 7.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 5.0.0.11 or later.
See remediation →
81/100
Remediation priority · High
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 PDF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code 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 PDF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-20390.

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

This is a memory corruption vulnerability in Kofax Power PDF's PDF file parser. The application fails to properly validate user-supplied data during PDF parsing, allowing an out-of-bounds write operation past the end of an allocated buffer. Successful exploitation requires a victim to open a specially crafted malicious PDF file, enabling arbitrary code execution in the context of the current process.

MitigationUsers should avoid opening PDF files from untrusted sources and ensure Kofax Power PDF is updated when vendor patches become available. Implement endpoint detection and network monitoring for indicators of malicious PDF files.

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

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify Power PDF installation
    Search for Kofax Power PDF or Tungstenautomation Power PDF in the system's installed programs. On Windows, check Programs and Features, or search for the application in common installation paths such as C:\Program Files\Kofax\ or C:\Program Files\Tungsten Automation\.
    Affected if Kofax Power PDF or Tungstenautomation Power PDF is present on the system
  2. Locate Power PDF executable
    Find the main Power PDF executable file (typically named PowerPDF.exe). Use Windows Explorer or run: dir "C:\Program Files\Kofax\Power PDF\*.exe" /s /b or the equivalent path for Tungsten Automation.
    Affected if The Power PDF executable file exists on the system
  3. Check file version
    Right-click the PowerPDF.exe file, select Properties, then go to the Details tab to view the File Version. Alternatively, right-click the application in Programs and Features and select Properties to view the Version information.
    Affected if The version displayed is less than 5.0.0.11 or cannot be determined

If Kofax Power PDF or Tungstenautomation Power PDF is installed with a version below 5.0.0.11, the environment is affected by this vulnerability when users open malicious PDF files.

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.

From vendor data
Upgrade available Upgrade to 5.0.0.11 or later
Fixed in 5.0.0.11
Interim mitigation

Users should avoid opening PDF files from untrusted sources and ensure Kofax Power PDF is updated when vendor patches become available. Implement endpoint detection and network monitoring for indicators of malicious PDF files.

Fix this in Power Pdf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-37334 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