dbcve.org
Jbig2decApplication · Artifex

CVE-2017-7975

HIGH · 7.8 CVSS v3.0 Published 2017-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Artifex jbig2dec 0.13, as used in Ghostscript, allows out-of-bounds writes because of an integer overflow in the jbig2_build_huffman_table function in jbig2_huffman.c during operations on a crafted JBIG2 file, leading to a denial of service (application crash) or possibly execution of arbitrary code.

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

Integer overflow in jbig2_build_huffman_table() when parsing crafted JBIG2 files causes heap-based out-of-bounds memory write, leading to potential denial of service or arbitrary code execution.

MitigationUpgrade jbig2dec to version 0.14 or later; also ensure Ghostscript is updated to a version incorporating the patched library.

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
Jbig2decApplication
Affected:= 0.13

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

CVSS:3.0/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 checks

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

  1. Identify jbig2dec library installation
    Run 'dpkg -l | grep jbig2dec' on Debian-based systems, or 'rpm -qa | grep jbig2dec' on RHEL-based systems, or check for libjbig2dec.so in /usr/lib/
    Affected if jbig2dec version 0.13 is installed
  2. Determine jbig2dec version
    Run 'jbig2dec -v' or 'jbig2dec --version' to output the version number
    Affected if Version returned is 0.13 exactly
  3. Check Ghostscript JBIG2 support
    Run 'gs --version' to get Ghostscript version, then run 'gs -h 2>&1 | grep -i jbig' to check if JBIG2 support is listed as available
    Affected if Ghostscript is present and has JBIG2 support enabled, combined with jbig2dec 0.13 on the system
  4. Inspect linked jbig2dec library
    Run 'ldd /usr/bin/gs 2>/dev/null | grep jbig' or 'ldd $(which gs) 2>/dev/null | grep jbig' to see which jbig2dec library Ghostscript links against
    Affected if Links to libjbig2dec.so.0.13 or version 0.13 shown

You are affected if jbig2dec version 0.13 is installed on your system, or if Ghostscript with JBIG2 support is running against the vulnerable 0.13 library version.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade jbig2dec to version 0.14 or later; also ensure Ghostscript is updated to a version incorporating the patched library.

Fix this in Jbig2dec Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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