Breaking: Java4Shell (CVE-2026-114938) - 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-2017-9611

ghostscript: Heap-buffer over-read in the Ins_MIRP function

Overview

Published
26 Jul 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
8 OS packages
4 Linux distributions
Yes Fix available

Description

The Ins_MIRP function in base/ttinterp.c in Artifex Ghostscript GhostXPS 9.21 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) or possibly have unspecified other impact via a crafted document.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-125

Affected packages · 0

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

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
ghostscript
Red Hat fixes for CVE-2017-9611
ReleasePackageFixed in
7 ghostscript +6 wont fix

debian 5 releases · 1 package

fixed 5
ghostscript
debian fixes for CVE-2017-9611
ReleasePackageFixed in
11 ghostscript 9.22~dfsg-1
12 ghostscript 9.22~dfsg-1
13 ghostscript 9.22~dfsg-1
14 ghostscript 9.22~dfsg-1
9 ghostscript 9.20~dfsg-3.2+deb9u1

echo 1 release · 1 package

fixed 1
ghostscript
echo fixes for CVE-2017-9611
ReleasePackageFixed in
ghostscript 9.22~dfsg-1

root.io debian 2 releases · 1 package

fixed 2
rootio-ghostscript
root.io debian fixes for CVE-2017-9611
ReleasePackageFixed in
12 rootio-ghostscript 9.22~dfsg-1
13 rootio-ghostscript 9.22~dfsg-1

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.