CVE-2024-12547
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 · uneditedTungsten Automation Power PDF JPF File Parsing Out-Of-Bounds Write 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 JPF 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-25560.
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 confidenceThis is an out-of-bounds write vulnerability in Tungsten Automation Power PDF's JPF file parser. The lack of proper validation of user-supplied data during JPF parsing allows an attacker to write past the end of an allocated buffer, potentially achieving arbitrary code execution in the context of the current process. Exploitation requires the user to open a malicious JPF file.
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< 5.1.1.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Power PDF installationCheck if Tungsten Automation Power PDF is installed on the system by looking in Program Files or Program Files (x86) for a Power PDF folder, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Power PDF entriesAffected if Power PDF is not installed on the system
-
Determine installed versionLocate the Power PDF installation directory and find the version information in the application executable properties (right-click the main .exe file and select Properties > Details), or check the uninstall registry key for the Version valueAffected if The installed version cannot be determined or verified
-
Compare version against vulnerability thresholdCompare the identified version number to 5.1.1.2 using standard version comparison (for example, 5.1.0.0, 5.1.0.1, 5.1.1.0, and 5.1.1.1 are all less than 5.1.1.2)Affected if The installed version is less than 5.1.1.2 (for example, 5.1.1.1, 5.1.0.0, or any 5.0.x.x release)
-
Confirm JPF file handling capabilityAttempt to locate JPF-related DLL files within the Power PDF installation directory (such as files containing 'jpf' in the name) or check if the application can open .jpf file associationsAffected if JPF file parsing components are present and the application can process JPF files
You are affected if Tungsten Automation Power PDF is installed with a version lower than 5.1.1.2 and the JPF file parser component is present on the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.1.1.2
Avoid opening untrusted JPF files from unknown sources. Apply vendor patches when available and consider endpoint detection solutions capable of monitoring for suspicious file processing activity.
Power PDF version 5.1.1.2 or later
- Upgrade Power PDF to version 5.1.1.2 or later to address the out-of-bounds write vulnerability in JPF file parsing
- Verify the upgrade by checking the application version in the About section
- Exercise caution when opening JPF files from untrusted sources, as user interaction is required to exploit this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12547 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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