dbcve.org
Jbig2decApplication · Artifex

CVE-2017-7976

HIGH · 7.1 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 →
74/100
Remediation priority · Elevated
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 allows out-of-bounds writes and reads because of an integer overflow in the jbig2_image_compose function in jbig2_image.c during operations on a crafted .jb2 file, leading to a denial of service (application crash) or disclosure of sensitive information from process memory.

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 jbig2dec 0.13's jbig2_image_compose function in jbig2_image.c allows out-of-bounds read/write operations when processing maliciously crafted .jb2 files, potentially causing denial of service or exposing sensitive process memory.

MitigationUpgrade jbig2dec to a patched version (post-0.13) or sanitize/reject untrusted .jb2 files before processing.

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
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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. Locate jbig2dec installation
    Run 'jbig2dec -v' or 'jbig2dec -h' to get the version, or check package manager listings (dpkg -l | grep jbig2dec, rpm -qa | grep jbig2dec)
    Affected if jbig2dec is installed and returns version 0.13
  2. Verify exact version number
    Compare the installed version to the affected range. The vulnerability affects only version 0.13 exactly
    Affected if The installed version is exactly 0.13
  3. Identify jbig2_image.c usage
    Check if any software links against or calls the jbig2_image_compose function from jbig2_image.c. Review application dependencies or memory-safe language bindings
    Affected if Code calls the jbig2_image_compose function from jbig2dec library
  4. Determine .jb2 file processing activity
    Audit the system for applications that process .jb2 files (PDF viewers, image converters, document processing tools). Check process logs, file access patterns, or application configurations for .jb2 handling
    Affected if The system or any application processes untrusted .jb2 files

User is affected if jbig2dec version 0.13 is installed AND the system processes .jb2 files through the vulnerable jbig2_image_compose function

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 a patched version (post-0.13) or sanitize/reject untrusted .jb2 files before processing.

Fix this in Jbig2dec Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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