Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1626193 - (CVE-2018-16585) CVE-2018-16585 ghostscript: .setdistillerkeys PostScript command is accepted even though it is not intended for use
CVE-2018-16585 ghostscript: .setdistillerkeys PostScript command is accepted ...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180906,reported=2...
: Security
Depends On: 1626195 1626194
Blocks: 1619570 1626196
  Show dependency treegraph
 
Reported: 2018-09-06 13:34 EDT by Pedro Sampaio
Modified: 2018-10-31 21:32 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pedro Sampaio 2018-09-06 13:34:31 EDT
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
Comment 1 Pedro Sampaio 2018-09-06 13:35:03 EDT
Created ghostscript tracking bugs for this issue:

Affects: fedora-all [bug 1626194]
Comment 3 David Kaspar [Dee'Kej] 2018-09-07 05:23:32 EDT
So, looking at the commits... The issue was discovered prior to 9.24, which means that for 9.24 (F28+) it is already fixed.

Note You need to log in before you can comment on or make changes to this bug.