CVE-2017-7885
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 · uneditedArtifex jbig2dec 0.13 has a heap-based buffer over-read leading to denial of service (application crash) or disclosure of sensitive information from process memory, because of an integer overflow in the jbig2_decode_symbol_dict function in jbig2_symbol_dict.c in libjbig2dec.a during operation on a crafted .jb2 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 confidenceA heap-based buffer over-read vulnerability exists in Artifex jbig2dec version 0.13 within the jbig2_decode_symbol_dict function in jbig2_symbol_dict.c (libjbig2dec.a). The flaw is caused by an integer overflow when processing a crafted .jb2 file, leading to potential denial of service (application crash) or disclosure of sensitive information from process memory.
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= 0.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify jbig2dec versionRun 'jbig2dec -v' or check the library version using 'strings libjbig2dec.a | grep -i version' or 'dpkg -l | grep jbig2dec' (Debian) or 'rpm -qa | grep jbig2dec' (RHEL)Affected if The installed version is exactly 0.13
-
Locate the jbig2dec library fileSearch for libjbig2dec using 'find / -name "*jbig2dec*" -o -name "libjbig2*" 2>/dev/null' to identify if the library is present on the systemAffected if libjbig2dec.a or libjbig2dec.so exists on the system at any location
-
Identify applications using jbig2decCheck application dependencies using 'ldd <application_binary>' or review any software that processes JBIG2 image files (commonly found in PDF viewers, Ghostscript, or image processing tools)Affected if Any application linked against libjbig2dec is in use
-
Determine if .jb2 file processing is enabledReview application configuration for JBIG2 decoding support; test by attempting to process a .jb2 file with jbig2dec: 'jbig2dec -o output.png input.jb2'Affected if JBIG2 decoding is enabled and .jb2 files can be processed by the application
-
Check source code version if availableIf jbig2dec source is present, verify jbig2_symbol_dict.c version: 'grep -i "version" jbig2_symbol_dict.c' or check the Makefile for version 0.13Affected if The source code version in jbig2_symbol_dict.c corresponds to version 0.13
The environment is affected if jbig2dec version 0.13 is installed and any application can process .jb2 files using the vulnerable library.
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.
From vendor dataUpdate jbig2dec to a patched version if available; otherwise, implement strict input validation to reject untrusted .jb2 files or disable JBIG2 decoding in affected applications until a fix can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7885 — 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-2017-7885 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