dbcve.org
Power PdfApplication · Tungstenautomation

CVE-2024-9751

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 5.1.0.1 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
Tungsten Automation Power PDF JP2 File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Tungsten Automation 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 proper validation of user-supplied data, which can result in a read 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-24468.

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

An out-of-bounds read vulnerability exists in Tungsten Automation Power PDF's JP2 (JPEG 2000) file parser due to insufficient validation of user-supplied data. The lack of proper bounds checking allows attackers to read past the end of allocated memory objects, potentially enabling arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted or unsolicited JP2 files until an official vendor patch is released. Implement application whitelisting and disable file preview features to reduce attack surface.

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

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
    Check for Power PDF in Add/Remove Programs (appwiz.cpl), or look in C:\Program Files\Tungsten Power PDF or C:\Program Files (x86)\Tungsten Power PDF for the executable. Also check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Power PDF entries.
    Affected if Power PDF is not installed or no version information is found.
  2. Determine installed version number
    Right-click the Power PDF executable (typically PowerPDF.exe or similar), select Properties, and check the Details tab for File Version. Alternatively, right-click in Add/Remove Programs and select Properties to view the installed version.
    Affected if Unable to retrieve version information.
  3. Compare version against affected range
    Compare your installed version to 5.1.0.1. If the version is lower (e.g., 5.0.x, 4.x.x) or if the version string indicates a build before 5.1.0.1, the installation is within the affected range.
    Affected if Installed version is 5.1.0.0 or lower, or any version below 5.1.0.1.
  4. Check JP2 file handling capability
    Open Power PDF and attempt to open a valid JP2/JPEG 2000 image file, or check file associations for .jp2 files pointing to Power PDF. Also verify if the application has preview or thumbnail generation enabled for image files.
    Affected if JP2 files can be opened, previewed, or processed by Power PDF.
  5. Identify user exposure to untrusted JP2 files
    Audit workflow patterns: determine if users routinely open JP2 files from external sources, email attachments, or untrusted network locations. Check if Power PDF is set as the default handler for JP2 files.
    Affected if Users open JP2 files from untrusted or external sources without additional scanning.

You are affected if Power PDF version is below 5.1.0.1 AND the application can process JP2 files, especially if users open JP2 files from untrusted sources.

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.1.0.1 or later
Fixed in 5.1.0.1
Interim mitigation

Avoid opening untrusted or unsolicited JP2 files until an official vendor patch is released. Implement application whitelisting and disable file preview features to reduce attack surface.

Recommended fix Moderate confidence

Power PDF 5.1.0.1 or later

  1. 1. Close all instances of Power PDF
  2. 2. Download Power PDF version 5.1.0.1 or later from the official Tungsten Automation website
  3. 3. Run the installer and follow the on-screen prompts to complete the upgrade
  4. 4. Restart your computer if prompted by the installer
  5. 5. After installation, verify the version by opening Power PDF and checking About/Version information

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

Fix this in Power Pdf Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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