A null pointer vulnerability was found in memgetbitsrectangle() when trying to read from unallocated memory.
Upstream bug:
https://bugs.ghostscript.com/showbug.cgi?id=697676
Upstream patch:
http://git.ghostscript.com/?p=ghostpdl.git;h=309eca4e0a31ea70dcc844812691439312dad091
The memgetbitsrectangle function in base/gdevmem.c in Artifex Software, Inc. Ghostscript 9.20 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file.
Last updated 25 August 2025
Ghostscript before 9.21rc1 permits the status command even if -dSAFER is used, which can allow remote attackers to determine the existence and size of arbitrary files.
Upstream bug:
https://bugs.ghostscript.com/showbug.cgi?id=697193
Upstream patch:
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=b60d50b7567369ad856cebe1efb6cd7dd2284219
If you call .sethalftone5 with an empty operand stack, ghostscript crashes. This flaw could be exploitable
Upstream bug : - Bug 697203 - NULL dereference in .sethalftone5 http://bugs.ghostscript.com/showbug.cgi?id=697203
Upstream patch : - Bug 697203: check for sufficient params in .sethalftone5 http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=f5c7555c303
Reference : http://seclists.org/oss-sec/2016/q4/98
The PS Interpreter in Ghostscript 9.18 and 9.20 allows remote attackers to execute arbitrary code via crafted userparams.
An incorrect reference count was found in .setdevice. This leads to a use-after-free, triggering a Denial of Service, or possibly, arbitrary code execution.
Upstream bug : - Bug 697179 - double free with .setdevice http://bugs.ghostscript.com/showbug.cgi?id=697179
upstream fix : - Bug 697179: Reference count device icc profile when copying a device http://git.ghostscript.com/?p=user/chrisl/ghostpdl.git;a=commitdiff;h=d5ad1e02
Reference : http://seclists.org/oss-sec/2016/q4/37
Ghostscript before 9.21 might allow remote attackers to bypass the SAFER mode protection mechanism and consequently read arbitrary files via the use of the .libfile operator in a crafted postscript document.
.initializedscparser doesn't validate the parameter is a dict type before using it.
This is a security issue, because it can be abused to escape the -dSAFER sandbox.
This allows a Denial of Service, arbitrary code execution.
Upstream bug : - Bug 697190 - .initializedscparser doesn't validate the parameter is a dict type before using it. http://bugs.ghostscript.com/showbug.cgi?id=697190
Upstream patch : - DSC parser - validate parameters http://git.ghostscript.com/?p=ghostpdl.git;h=875a0095f37626a721c7ff57d606a0f95af03913
Reference : http://seclists.org/oss-sec/2016/q4/37