CVE-2023-38079
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 · uneditedKofax Power PDF JP2 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Kofax 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 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-20485.
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 confidenceKofax Power PDF contains an out-of-bounds write vulnerability in its JP2 (JPEG 2000) file parser. The parser fails to properly validate user-supplied data before writing to memory, allowing an attacker to write past the end of an allocated buffer. Exploitation requires the user to open a malicious JP2 file or visit a webpage containing one, leading to arbitrary code execution in the context of the current 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.0.0.10CVSS 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.0/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.
-
Check installed Power PDF versionLocate the Power PDF application in the system programs list, or check the file properties of the main executable (commonly found in Program Files\Kofax or Program Files\Tungsten Automation\Power PDF). Compare the version number to the affected range below 5.0.0.10.Affected if The installed version is below 5.0.0.10
-
Confirm JP2 file handling is activeTest whether the application can open or preview .jp2 files by attempting to load a sample JP2 image, or check the application's file association settings to confirm JP2 is registered as a supported format.Affected if JP2 files are associated with Power PDF and can be opened or previewed within the application
-
Verify file preview functionalityCheck if Power PDF's embedded preview or thumbnail generation feature is enabled for image files. This can typically be found in the application's preferences or settings under file handling, preview, or security categories.Affected if Automatic preview or thumbnail generation for image files including JP2 is enabled
A system is affected if Power PDF version is below 5.0.0.10 AND the application can open, parse, or generate previews for JP2 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.0.0.10
Apply the vendor patch when available. Avoid opening JP2 files from untrusted sources and consider disabling automatic file preview features. Ensure endpoint protection is active.
Power PDF 5.0.0.10 or later
- 1. Close any running instances of Kofax Power PDF
- 2. Download Power PDF version 5.0.0.10 or later from the official Kofax website or your licensed distribution channel
- 3. Run the installer and follow the prompts to upgrade
- 4. Verify the installation by checking Help > About Power PDF to confirm the version number
- 5. Open the application and ensure normal functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2023-38079 — 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-2023-38079 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