CVE-2024-5512
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 JP2 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 JP2 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-22021.
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 confidenceOut-of-bounds read vulnerability in Kofax Power PDF's JP2 file parser. Due to insufficient validation of user-supplied data during JP2 parsing, an attacker can read past the end of an allocated object, leading to information disclosure. While the primary impact is information disclosure, the advisory notes this can be chained with other vulnerabilities for 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.21CVSS 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.
-
Locate installed Power PDF versionOpen Windows Control Panel > Programs and Features, or right-click the Power PDF executable in Program Files > Properties > Details to see the version. Alternatively, run 'wmic product get name,version' or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Power PDF entries.Affected if Version listed is below 5.0.0.21
-
Confirm JP2 file handling is possibleVerify the Power PDF installation includes the JP2 (JPEG 2000) codec or image filter. Check if the program can open or preview .jp2 files, or examine installed file type handlers in the application data folder.Affected if The application can process JP2 files and the version is below 5.0.0.21
-
Check for recent file processing activityReview recent documents opened in Power PDF, check application logs or temp folders for recently processed JP2 files, or examine the application's recent files list.Affected if JP2 files were opened with an affected version of Power PDF
You are affected if Power PDF version is below 5.0.0.21 and you have opened or processed JP2 files with the vulnerable application.
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.21
Apply vendor-supplied patches/updates for Kofax Power PDF when available. Until then, avoid opening untrusted or originate JP2 files from unknown sources, and disable automatic file opening in the application.
Power PDF 5.0.0.21 or later
- Identify the current installed version of Kofax Power PDF on the system
- Navigate to the official Kofax support website or software update mechanism
- Download and install Power PDF version 5.0.0.21 or later
- Verify the installed version matches or exceeds 5.0.0.21
- Ensure users are educated not to open untrusted JP2 files from unknown sources as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5512 — 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-5512 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