dbcve.org
PopplerApplication · Freedesktop

CVE-2013-7296

MEDIUM · 5.0 CVSS v2.0 Published 2014-01-26
Fix available
A fix is available. Upgrade to after 0.24.3 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
The JBIG2Stream::readSegments method in JBIG2Stream.cc in Poppler before 0.24.5 does not use the correct specifier within a format string, which allows context-dependent attackers to cause a denial of service (segmentation fault and application crash) via a crafted PDF file.

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 confidence

A format string vulnerability exists in the JBIG2Stream::readSegments method in Poppler's JBIG2Stream.cc. The method uses an incorrect format specifier, causing a segmentation fault and application crash when processing a crafted PDF file containing malicious JBIG2 image data.

MitigationUpgrade Poppler to version 0.24.5 or later. Until upgraded, exercise caution when opening PDF files from untrusted sources.

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
PopplerApplication
Affected:<= 0.24.3= 0.1= 0.1.1= 0.1.2= 0.2.0= 0.10.0= 0.10.1= 0.10.2= 0.10.3= 0.10.4= 0.10.5= 0.10.6

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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Check if Poppler is installed
    Run `poppler-config --version` or check your system's package manager for the poppler package (e.g., `dpkg -l | grep poppler` or `rpm -qa | grep poppler`)
    Affected if Poppler is not installed on the system
  2. Determine installed Poppler version
    Execute `poppler-config --version` or look up the version from the package manager query performed in step 1
    Affected if The version is 0.24.3 or lower, or matches any of these specific versions: 0.1, 0.1.1, 0.1.2, 0.2.0, 0.10.0, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.10.5, or 0.10.6
  3. Verify JBIG2 support is enabled
    Run `poppler-config --libs` and look for jbig2dec in the output, or check if the JBIG2Stream.cc component was compiled into the Poppler library (examine the binary or library file for JBIG2-related symbols)
    Affected if JBIG2 support is compiled into Poppler and the vulnerable code path can be triggered

If Poppler is installed with a version matching the affected list and JBIG2 support is enabled, the environment is vulnerable to CVE-2013-7296 when processing malicious PDF files.

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 0.24.3
Interim mitigation

Upgrade Poppler to version 0.24.5 or later. Until upgraded, exercise caution when opening PDF files from untrusted sources.

Fix this in Poppler Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7296 — 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-2013-7296 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