dbcve.org
Power PdfApplication · Tungstenautomation

CVE-2024-27346

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 5.0.0.17 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 PDF File Parsing Out-Of-Bounds Read 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 handling of PDF 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 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-22934.

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 an out-of-bounds read vulnerability in Kofax Power PDF's PDF file parsing functionality. The vulnerability stems from insufficient validation of user-supplied data during PDF processing, which allows reading past the end of an allocated buffer. While the primary impact is information disclosure, the advisory notes this can be chained with other vulnerabilities to achieve arbitrary code execution in the current process context.

MitigationApply the vendor-provided patch or update Kofax Power PDF to the latest version. Until patched, avoid opening PDF files from untrusted sources and exercise caution with email attachments or downloads from unknown origins.

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

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. Identify if Kofax or Tungstenautomation Power PDF is installed
    Check the system for Power PDF installation: Look in Program Files (e.g., C:\Program Files\Kofax\Power PDF or C:\Program Files\Tungsten Power PDF) or open Control Panel > Programs and Features and search for 'Power PDF' or 'Kofax' in the installed programs list.
    Affected if Power PDF or Kofax Power PDF appears in the installed programs list or the installation directory exists.
  2. Locate the Power PDF executable to check its version
    Navigate to the Power PDF installation directory (typically C:\Program Files\Kofax\Power PDF\bin) and locate the main executable (often named PowerPDF.exe or similar). Right-click the executable, select Properties, then click the Details tab to view the File Version.
    Affected if The executable file exists at the expected path.
  3. Compare the installed version against the affected range
    Note the File Version shown in the Details tab. Compare it numerically to version 5.0.0.17. Versions earlier than 5.0.0.17 (such as 5.0.0.16, 4.0.x.x, 3.x.x, etc.) are affected. Versions at or above 5.0.0.17 are not affected.
    Affected if The installed version is a version number less than 5.0.0.17 (e.g., 5.0.0.16, 4.0.0.0, etc.).
  4. Verify PDF processing capability is present
    The vulnerability exists in the PDF parsing component. If Power PDF is installed and can open or process PDF files, the vulnerable code path is present in the environment. Launch Power PDF and attempt to open a PDF file to confirm the application is functional.
    Affected if The application can open and process PDF documents.

If Power PDF is installed and the version is below 5.0.0.17, the environment is affected by this vulnerability.

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.17 or later
Fixed in 5.0.0.17
Interim mitigation

Apply the vendor-provided patch or update Kofax Power PDF to the latest version. Until patched, avoid opening PDF files from untrusted sources and exercise caution with email attachments or downloads from unknown origins.

Recommended fix Moderate confidence

Power PDF version 5.0.0.17 or later

  1. Identify the current version of Power PDF installed on the system
  2. Navigate to the official Kofax support or download page to obtain version 5.0.0.17 or later
  3. Download and install Power PDF version 5.0.0.17 or the latest available version
  4. Restart the application and verify the version number reflects the update

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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