CVE-2023-38077
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 U3D File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information 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 U3D 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 in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-20471.
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 missing bounds check in Kofax Power PDF's U3D file parser allows reading past the end of an allocated buffer when parsing specially crafted U3D files. This out-of-bounds read exposes sensitive memory contents to an attacker who tricks a user into opening a malicious 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.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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 for the presence of Power PDF in the installed programs list. On Windows, open Control Panel > Programs and Features or run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName | Where-Object {$_ -like '*Power PDF*'}Affected if Power PDF is not installed on the system
-
Determine installed versionLocate the Power PDF executable and check its file version. Common paths: C:\Program Files\Kofax\Power PDF\Bin\PowerPDF.exe or C:\Program Files\Tungsten Automation\Power PDF\Bin\PowerPDF.exe. Right-click the .exe, select Properties, and check the Details tab for Product Version, or run: (Get-Item 'C:\Program Files\Kofax\Power PDF\Bin\PowerPDF.exe').VersionInfo.ProductVersionAffected if The installed version is lower than 5.0.0.10 (for example, 4.0.x.x or 5.0.0.x below 5.0.0.10)
-
Verify U3D file handling capabilityAttempt to open a benign U3D file or check if the application has U3D parsing libraries present. Examine the Power PDF installation directory for U3D-related DLL files (such as u3d*.dll) in the Bin folder. The presence of these files indicates U3D parsing is available.Affected if U3D parsing capability exists in the installation and the version is vulnerable
The system is affected if Power PDF is installed with a version lower than 5.0.0.10, as the missing bounds check in the U3D parser will be triggered when opening a malicious U3D file.
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. Until then, instruct users not to open untrusted U3D files and consider blocking U3D file attachments at the email gateway.
Power PDF 5.0.0.10 or later
- 1. Verify current Power PDF installation version via Help > About or program properties
- 2. Download Power PDF version 5.0.0.10 or later from the official Kofax website
- 3. Close all Power PDF instances and related applications
- 4. Run the installer with administrator privileges
- 5. Follow the installation wizard prompts to complete the upgrade
- 6. Restart the system if prompted
- 7. Verify the installed version is 5.0.0.10 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38077 — 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-38077 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