dbcve.org
Power PdfApplication · Tungstenautomation

CVE-2024-12549

HIGH · 7.8 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 5.1.1.2 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-25565.

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

Tungsten Automation Power PDF contains an out-of-bounds read vulnerability in its JP2 (JPEG 2000) file parsing logic. The application fails to properly validate user-supplied data during JP2 parsing, allowing an attacker to read past the end of an allocated buffer. This memory disclosure can be leveraged alongside memory corruption to achieve arbitrary code execution in the context of the current process.

MitigationAvoid opening JP2 files or PDF documents from untrusted sources. Apply vendor patches when available. Consider deploying additional sandboxing or application isolation for PDF processing workflows.

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

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 Tungsten Automation Power PDF in the application list or installed programs (typically at C:\Program Files\Tungsten Automation\Power PDF\ or C:\Program Files (x86)\Tungsten Automation\Power PDF\)
    Affected if Tungsten Automation Power PDF is installed on the system
  2. Determine installed version
    Right-click the Power PDF executable, select Properties, then look at the Details tab for Product Version, or open Power PDF and go to Help > About
    Affected if The version number is lower than 5.1.1.2 (for example, 5.0.x, 5.1.0.x, or 5.1.1.0)
  3. Confirm JP2 parsing is accessible
    Verify that the application can open and process JP2 (JPEG 2000) image files - this occurs when opening PDF documents containing JP2 images or when opening JP2 files directly through the application's File > Open dialog
    Affected if Users can open PDF files with embedded JP2 content or directly open JP2 image files using Power PDF

A system is affected if Tungsten Automation Power PDF is installed with a version lower than 5.1.1.2 and users can open PDF documents containing JP2 images or JP2 image files directly.

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.1.2 or later
Fixed in 5.1.1.2
Interim mitigation

Avoid opening JP2 files or PDF documents from untrusted sources. Apply vendor patches when available. Consider deploying additional sandboxing or application isolation for PDF processing workflows.

Recommended fix Moderate confidence

Power PDF 5.1.1.2 or later

  1. Navigate to the official Tungsten Automation support website or trusted software distribution channel for Power PDF
  2. Locate the download page for Power PDF version 5.1.1.2 or later
  3. Download the installer for the fixed version
  4. Verify the integrity of the downloaded installer using checksums if provided
  5. Close any running instances of Power PDF
  6. Run the installer and follow the prompts to upgrade to version 5.1.1.2 or later
  7. After installation, verify the version number matches the fixed release

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

Fix this in Power Pdf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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