An issue was discovered in Artifex Ghostscript before 9.24. The .setdistillerkeys PostScript command is accepted even though it is not intended for use during document processing (e.g., after the startup phase). This leads to memory corruption, allowing remote attackers able to supply crafted PostScript to crash the interpreter or possibly have unspecified other impact. References: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1497d65039885a52b598b137dd8622bd4672f9be http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=971472c83a345a16dac9f90f91258bb22dd77f22 https://seclists.org/oss-sec/2018/q3/182
Created ghostscript tracking bugs for this issue: Affects: fedora-all [bug 1626194]
So, looking at the commits... The issue was discovered prior to 9.24, which means that for 9.24 (F28+) it is already fixed.
It appears that this CVE description might not be correct : * ghostscript does not have a `.setdistillerkeys` command. This was probably a typo, the command targeted might probably be .setdistillerparams * the commits pointed by the CVE as a fix (971472c83a & 1497d650) are dated from gs-9.22 (2017), do not seem to seem to undefine any *distill* parameter, and .setdistillerparams appears to still be accessible after these commits. * From the above, I believe that the fix for this vulnerability might actually be http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b0a385475
The accessibility of .setdistillerparams does not really represent a security defect. This CVE is mostly a duplicate of CVE-2018-15910 (fixed via RHSA-2018:3834)
Statement: There are no .setdistillerkeys operator in ghostscript. It is suspected it might be a typo from .distillerparamkeys or .setdistillerparams. It was found that .distillerparamkeys and .setdistillerparams methods can be called although they are not intended to be used. However, the only known security threat they cause has been fixed via CVE-2018-15910.