CVE-2024-5305
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 PDF File Parsing 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 parsing of PDF files. 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-22921.
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 a stack-based buffer overflow vulnerability in its PDF file parsing component. The flaw occurs due to insufficient validation of user-supplied data length before copying to a fixed-size stack buffer, allowing remote attackers to achieve arbitrary code execution in the context of the current process via malicious 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.18CVSS 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.
-
Locate Kofax Power PDF installationCheck common installation directories (C:\Program Files\Kofax\Power PDF, C:\Program Files (x86)\Kofax\Power PDF) or search for executable files named 'Power PDF.exe' using dir /s command or Windows SearchAffected if The product is not installed in the expected locations or the executable is missing
-
Identify installed version via executable propertiesRight-click on Power PDF.exe, select Properties, then view the Details tab to see the Product Version field; alternatively run 'powershell (Get-Item "C:\Program Files\Kofax\Power PDF\Power PDF.exe").VersionInfo'Affected if The displayed version number is less than 5.0.0.18 (e.g., 5.0.0.17, 5.0.0.0, or any 4.x version)
-
Check Windows Registry for versionOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Kofax\Power PDF or HKEY_CURRENT_USER\SOFTWARE\Kofax\Power PDF, then look for a Version or DisplayVersion string valueAffected if The registry version value is less than 5.0.0.18
-
Verify PDF parsing functionality is presentConfirm the Power PDF application and its PDF parsing component are present and functional - attempt to open the application or check for PDF-related DLL files in the installation directory (e.g., PdfParser.dll, PDFCore.dll)Affected if The PDF parsing component exists and is executable (this is the vulnerable component)
-
Confirm no emergency workarounds are in placeCheck if the application is run from a restricted sandbox, has software-based execution restrictions, or if enterprise policies block PDF files from untrusted sourcesAffected if No additional runtime protections are actively mitigating the risk of opening malicious PDFs
A system is affected if Kofax Power PDF is installed with any version prior to 5.0.0.18 and the PDF parsing component is functional, as the buffer overflow can be triggered by opening a specially crafted malicious PDF 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.18
Apply the vendor-released patch for CVE-2024-5305 to Kofax Power PDF installations. Until the patch is available, instruct users to avoid opening untrusted PDF files from unknown sources.
Power PDF version 5.0.0.18 or later
- 1. Open Power PDF application
- 2. Navigate to Help > About Power PDF to check the current version number
- 3. If the version is below 5.0.0.18, download the latest version of Power PDF from the official Kofax website or your organization's software distribution center
- 4. Close all instances of Power PDF
- 5. Run the installer and follow the on-screen prompts to upgrade
- 6. After installation, verify the version by checking Help > About Power PDF confirms version 5.0.0.18 or higher
- 7. Test that PDF files open and function normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5305 — 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-5305 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