CVE-2023-51567
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 OXPS 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 OXPS 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-21988.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in Kofax Power PDF's OXPS file parsing. The lack of proper validation of user-supplied data during OXPS parsing allows reading past the end of an allocated object, leading to information disclosure. This can potentially be chained with other vulnerabilities to achieve arbitrary code execution.
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.16CVSS 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 Kofax Power PDF or Tungstenautomation Power PDF on the system. Look for the application in Add/Remove Programs (Windows) or inspect common installation paths such as C:\Program Files\Kofax\Power PDF or C:\Program Files\Tungsten Automation\Power PDF.Affected if The application is installed on the system.
-
Determine installed versionOpen Power PDF and navigate to Help > About, or right-click the executable and select Properties > Details to view the version number. Alternatively, check the version in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Power PDF entries.Affected if The installed version is lower than 5.0.0.16.
-
Check OXPS file handling capabilityVerify that the OXPS (Open XML Paper Specification) parsing module is available in the installation. OXPS support is typically built into the core application. Check the installation directory for oxps-related DLLs or confirm that the application can open .oxps files.Affected if OXPS parsing functionality is present in the installation.
-
Identify OXPS file processing workflowReview how the Power PDF installation processes OXPS files. Determine whether users or automated processes routinely open OXPS documents, particularly from external or untrusted sources.Affected if OXPS files from unknown or untrusted sources are processed by the application.
The environment is affected if Power PDF (or Tungstenautomation Power PDF) is installed with a version lower than 5.0.0.16 and the application processes OXPS files from any source.
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.16
Avoid opening untrusted OXPS files from unknown sources. Apply vendor patches when available.
5.0.0.16
- Upgrade Kofax Power PDF to version 5.0.0.16 or later to address the OXPS file parsing out-of-bounds read vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51567 — 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-51567 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