dbcve.org
Power PdfApplication · Tungstenautomation

CVE-2024-27334

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-02
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 JPG 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 parsing of JPG 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-21978.

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

An out-of-bounds read vulnerability exists in Kofax Power PDF's JPG file parsing functionality. The lack of proper validation of user-supplied data during JPG parsing allows reading past the end of an allocated object, leading to sensitive information disclosure. While primarily an information disclosure issue, this vulnerability can be chained with other flaws to achieve arbitrary code execution.

MitigationApply the vendor-supplied patch for Kofax Power PDF when available. Until then, avoid opening untrusted JPG files and consider disabling automatic file preview features in the PDF application.

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 installed Power PDF version
    Open Power PDF, go to Help > About Power PDF, or check the program's file properties (right-click the executable > Properties > Details). Look for the exact version number.
    Affected if The version number is lower than 5.0.0.17 (e.g., 5.0.0.16, 5.0.0.10, etc.)
  2. Confirm JPG parsing functionality is present
    Verify the Power PDF installation includes image conversion or import features. Check for installed plugins/modules related to image handling in the program's installation directory.
    Affected if JPG import/conversion modules are installed and the program can process JPG files
  3. Check for recent JPG file processing activity
    Review recently opened PDF documents that contain embedded or imported JPG images. In Power PDF, examine document history or temp folders for recent image imports.
    Affected if JPG files have been opened, imported, or previewed in Power PDF

You are affected if Power PDF version is below 5.0.0.17 and you open, import, or preview JPG files using the application.

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-supplied patch for Kofax Power PDF when available. Until then, avoid opening untrusted JPG files and consider disabling automatic file preview features in the PDF application.

Recommended fix Moderate confidence

Kofax Power PDF 5.0.0.17 or later

  1. 1. Determine the current installed version of Kofax Power PDF by opening the application and navigating to Help > About
  2. 2. If the version is below 5.0.0.17, download the latest version of Kofax Power PDF from the official vendor website
  3. 3. Close all instances of Power PDF before running the installer
  4. 4. Run the installer with administrative privileges
  5. 5. Follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the new version by checking Help > About

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
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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