CVE-2024-27336
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 PNG 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 PNG 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-22022.
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 confidenceAn out-of-bounds read vulnerability exists in Kofax Power PDF's PNG file parsing logic. The software fails to properly validate user-supplied data when processing PNG files, allowing an attacker to read past the end of an allocated buffer and disclose sensitive memory contents. While this vulnerability alone leads to information disclosure, it can 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.17CVSS 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 is installedCheck for the presence of Tungstenautomation Power PDF or Kofax Power PDF in the system. Look in Program Files or use Add/Remove Programs to list installed applications.Affected if The software is not found on the system, so this CVE does not apply.
-
Identify the installed versionOpen Power PDF, then go to Help > About, or right-click the executable in Program Files > Properties > Details to find the version number.Affected if Version is less than 5.0.0.17 - the vulnerability is present in these versions.
-
Verify PNG processing capability existsAttempt to insert or open a PNG file within Power PDF, or check the supported file formats in the application's options or import settings.Affected if PNG files can be processed or imported - the vulnerable parsing code path is accessible.
-
Check for any disabled image parsersReview Power PDF's security or file handling settings for any options that disable or restrict PNG file processing.Affected if PNG processing is not explicitly disabled - the vulnerable code can be triggered.
You are affected if Power PDF or Kofax Power PDF is installed with a version lower than 5.0.0.17 and the application can process PNG 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.17
Apply vendor-supplied patches for Kofax Power PDF when available. Until then, instruct users to avoid opening untrusted or suspicious PNG-containing PDF files from unknown sources.
Kofax Power PDF 5.0.0.17 or later
- 1. Check the currently installed version of Kofax Power PDF (Help > About or via the application menu)
- 2. Back up any important PDF files and application settings
- 3. Download Kofax Power PDF version 5.0.0.17 or later from the official Kofax website or authorized vendor channels
- 4. Run the installer and follow the on-screen prompts to upgrade the application
- 5. Verify the new version is correctly installed after completion
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27336 — 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-27336 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