dbcve.org
XpdfApplication · Xpdfreader

CVE-2024-7867

MEDIUM · 6.2 CVSS v3.1 Published 2024-08-15
Fix available
A fix is available. Upgrade to after 4.05 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
In Xpdf 4.05 (and earlier), very large coordinates in a page box can cause an integer overflow and divide-by-zero.

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 confidence

In Xpdf 4.05 and earlier, the PDF parser does not properly validate very large coordinates in page box definitions (such as MediaBox, CropBox, or similar). When coordinates exceed certain bounds, an integer overflow occurs that leads to a divide-by-zero condition, causing a denial of service or potentially other unspecified impact.

MitigationUpdate Xpdf to a version beyond 4.05 when available; otherwise, avoid processing untrusted PDF files with unusually large or malformed page box coordinates.

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
XpdfApplication
Affected:<= 4.05

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Xpdf is installed
    Run command: which xpdf (Linux/macOS) or where xpdf (Windows). If the command returns a path, Xpdf is installed.
    Affected if No path is returned for the xpdf command - the product is not installed.
  2. Determine installed Xpdf version
    Run: xpdf -v or xpdf -version. This displays the version number of the Xpdf binary.
    Affected if The command fails or returns no version information - Xpdf may not be properly installed.
  3. Compare version against affected range
    Check if the version number returned is 4.05 or any lower version (e.g., 4.04, 4.03, 4.02, 4.01, 4.00, 3.x). The affected range is <= 4.05.
    Affected if Version is 4.05 or lower - the installed version is within the affected range and may be vulnerable.

If Xpdf is installed and the version is 4.05 or lower, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 4.05
Interim mitigation

Update Xpdf to a version beyond 4.05 when available; otherwise, avoid processing untrusted PDF files with unusually large or malformed page box coordinates.

Fix this in Xpdf Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7867 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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