CVE-2023-38092
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 importDataObject Stack-based Buffer Overflow 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 implementation of the importDataObject method. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-20603.
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 confidenceA stack-based buffer overflow vulnerability exists in Kofax Power PDF's importDataObject method. The flaw results from insufficient bounds checking when copying user-supplied data to a fixed-length stack buffer, allowing an attacker to overwrite stack frames and achieve arbitrary code execution through specially crafted PDF files.
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 the installed Power PDF versionOpen Power PDF, then go to Help > About, or right-click the executable file (Power PDF.exe) and select Properties > Details to view the Product VersionAffected if The installed version is below 5.0.0.10
-
Locate the Power PDF executable version via command lineRun the command: wmic product where "name like 'Power PDF'" get name,version or check the file version using: powershell "(Get-Item 'C:\Program Files\Kofax\Power PDF\Power PDF.exe').VersionInfo.FileVersion"Affected if The version displayed is lower than 5.0.0.10
-
Verify the application is used in your environmentCheck for installed instances on endpoints using: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" /s /f "Power PDF" or check Program Files for the Kofax folderAffected if Power PDF version 5.0.0.10 or lower is found installed on the system
-
Determine if users process untrusted PDF documentsReview user workflows or security policies to identify if staff open PDF files from external sources, email attachments, or web downloadsAffected if Users routinely open PDF files from untrusted or unknown sources without prior scanning
The environment is affected if Power PDF version 5.0.0.10 or lower is installed and users open PDF documents, as the buffer overflow triggers when processing a specially crafted PDF file using the importDataObject method.
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
Users should avoid opening untrusted or unexpected PDF files, as exploitation requires user interaction to open a malicious document. Organizations should apply vendor-provided patches and ensure updates are deployed through standard patch management processes.
Power PDF 5.0.0.10 or later
- 1. Open Kofax Power PDF application
- 2. Navigate to Help > About Power PDF to check current version
- 3. If version is below 5.0.0.10, download the latest version from the official Kofax website or your vendor portal
- 4. Run the installer and follow the prompts to upgrade
- 5. Verify the installed version is 5.0.0.10 or later after upgrade completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38092 — 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-38092 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