# CVE-2024-12547: Tungsten Automation Power PDF JPF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into opening malicious JPF files in Power PDF.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-p3w4-g6w7-3v89

## What is CVE-2024-12547?

CVE-2024-12547 is a high-severity memory corruption vulnerability in Tungstenautomation Power Pdf, published on 11 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-12547?

It affects 1 product.


Products: Tungstenautomation Power Pdf.

## How do I fix CVE-2024-12547?

No fix has been published for CVE-2024-12547 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-12547 being exploited?

There is no known exploitation of CVE-2024-12547 in the wild and no public exploit code.

## Other vulnerabilities in Tungstenautomation Power Pdf

- [CVE-2024-12549](https://insights.sbomify.com/CVE-2024-12549/): Tungsten Automation Power PDF JP2 File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability (high 7.8)
- [CVE-2024-12551](https://insights.sbomify.com/CVE-2024-12551/): Tungsten Automation Power PDF JP2 File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability (high 7.8)
- [CVE-2024-5510](https://insights.sbomify.com/CVE-2024-5510/): Kofax Power PDF JP2 File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability (high 7.8)
- [CVE-2024-5511](https://insights.sbomify.com/CVE-2024-5511/): Kofax Power PDF JP2 File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability (high 7.8)
- [CVE-2024-5513](https://insights.sbomify.com/CVE-2024-5513/): Kofax Power PDF JP2 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12547 and fix it if it is affected.

What it is: CVE-2024-12547 is a high-severity memory corruption vulnerability in Tungstenautomation Power Pdf, published on 11 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-12547 in the wild and no public exploit code.

Affected product: Tungstenautomation Power Pdf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-12547/ (Markdown: https://insights.sbomify.com/CVE-2024-12547/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-12547
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-12547
- OSV: https://osv.dev/vulnerability/CVE-2024-12547

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-12547/
Summaries are generated and may contain mistakes; the official description above is the record.