CVE-2024-9755
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 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-24472.
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 confidenceAn out-of-bounds read vulnerability exists in Tungsten Automation Power PDF's JP2 file parsing logic. The flaw results from insufficient validation of user-supplied data during JP2 image processing, allowing an attacker to read past the end of an allocated memory buffer. This memory disclosure can be leveraged to achieve arbitrary code execution in the context of the current user process.
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.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Power PDF installationCheck if Tungsten Automation Power PDF is installed on the system by looking for the application in installed programs or searching for executables named 'Power PDF' or related binariesAffected if The software is not installed means not affected
-
Identify installed versionAccess the program's About or Help section, or check the Windows Add/Remove Programs list to locate the exact version number of Power PDFAffected if Version is less than 5.1.0.1 indicates the system is vulnerable
-
Determine JP2 processing usageCheck if the environment involves processing JP2 (JPEG 2000) image files through Power PDF, such as opening JP2 attachments or converting JP2 documentsAffected if JP2 files are regularly processed or opened with Power PDF means the exploit surface is active
-
Verify patch statusContact Tungsten Automation support or check release notes for version 5.1.0.1 to confirm whether the installed version includes the security fixAffected if No official patch has been applied to version 5.1.0.1 or later means the vulnerability remains exploitable
A system is affected if Tungsten Automation Power PDF is installed with a version below 5.1.0.1 and routinely processes JP2 image files.
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.0.1
Restrict processing of untrusted JP2 files until an official vendor patch is available; implement file type screening or sandboxing for JP2 attachments as a defensive layer.
Power PDF 5.1.0.1 or later
- 1. Identify the current version of Power PDF installed on the system
- 2. Navigate to the official Tungsten Automation support or download page for Power PDF
- 3. Download Power PDF version 5.1.0.1 or a later stable release
- 4. Ensure all user interaction with the application is avoided until the update is applied
- 5. Run the installer and follow the prompts to upgrade Power PDF
- 6. After installation, verify the new version number in the application's About section
- 7. Train users to avoid opening untrusted JP2 files from unknown sources as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9755 — 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-9755 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