CVE-2022-24107
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 · uneditedXpdf prior to 4.04 lacked an integer overflow check in JPXStream.cc.
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 confidenceXpdf before version 4.04 contains an integer overflow vulnerability in JPXStream.cc, the component responsible for parsing JPEG2000 image streams embedded in PDF files. The missing bounds check could allow a specially crafted PDF with a malicious JPX stream to trigger heap corruption, potentially leading to arbitrary code execution when the file is opened.
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< 4.04CVSS 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.
-
Check if Xpdf is installedRun 'xpdf -v' or 'xpdf -help' in a terminal, or check your system's package manager for installed packages named xpdfAffected if Xpdf is found on the system
-
Identify installed Xpdf versionExecute 'xpdf -v' and note the version number in the output, or query your package manager with 'dpkg -l xpdf' or 'rpm -qi xpdf'Affected if The version number displayed is below 4.04
-
Confirm JPX parsing is availableThe vulnerability exists in the JPXStream.cc component used for parsing JPEG2000 image streams in PDFs - this functionality is built into all Xpdf versions before 4.04 and requires no special configuration to be presentAffected if Xpdf is installed with any functionality to render PDF files containing images
If Xpdf is installed and its version is lower than 4.04, the environment is vulnerable when opening specially crafted PDF files with malicious JPX streams.
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 · scoped4.04
Update Xpdf to version 4.04 or later to obtain the integer overflow check. If immediate patching is not possible, exercise caution when opening PDF files from untrusted sources.
4.04
- 1. Identify the currently installed Xpdf version by running 'xpdf -v' or checking your package manager.
- 2. Download Xpdf version 4.04 or later from the official website www.xpdfreader.com or dl.xpdfreader.com.
- 3. If using a package manager, check for available updates and upgrade to the latest version (4.04 or later).
- 4. If installing from source, download the source tarball for version 4.04 or later, extract it, and follow the build instructions in the README file.
- 5. After upgrading, verify the new version is installed by running 'xpdf -v'.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24107 — 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-2022-24107 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