Breaking: Java4Shell - Easy to Crash, Hard to Exploit. Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-9601

ghostscript: Heap-buffer overflow due to Integer overflow in jbig2_image_new function

Overview

Published
24 Apr 2018
Modified
17 Jun 2026
Medium CVE
0 Registry packages
9 OS packages
4 Linux distributions
Yes Fix available

Description

ghostscript before version 9.21 is vulnerable to a heap based buffer overflow that was found in the ghostscript jbig2_decode_gray_scale_image function which is used to decode halftone segments in a JBIG2 image. A document (PostScript or PDF) with an embedded, specially crafted, jbig2 image could trigger a segmentation fault in ghostscript.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-190, CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 7 fixes

Red Hat 1 release · 1 package

wont fix 1
ghostscript
Red Hat fixes for CVE-2016-9601
ReleasePackageFixed in
7 ghostscript +6 wont fix

debian 4 releases · 1 package

fixed 4
jbig2dec
debian fixes for CVE-2016-9601
ReleasePackageFixed in
11 jbig2dec 0.13-4
12 jbig2dec 0.13-4
13 jbig2dec 0.13-4
14 jbig2dec 0.13-4

echo 1 release · 1 package

fixed 1
jbig2dec
echo fixes for CVE-2016-9601
ReleasePackageFixed in
jbig2dec 0.13-4

root.io debian 1 release · 1 package

fixed 1
rootio-jbig2dec
root.io debian fixes for CVE-2016-9601
ReleasePackageFixed in
12 rootio-jbig2dec 0.13-4

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.