https://seclists.org/oss-sec/2018/q3/229
Affected Software
Frequently Asked Questions
What does an attacker need to exploit this issue?
An attacker needs Ghostscript to process a crafted PostScript file. The supplied proof of concept fills the operand stack to trigger a stack overflow while handling page-device parameters.
Is running Ghostscript with -dSAFER sufficient protection?
No. The proof of concept is shown running with -dSAFER and uses the error path to leave the page device in an insecure state, allowing a %pipe% output target.
What can be done if an updated package is not immediately available?
Do not process untrusted PostScript input with the affected Ghostscript build. The issue is fixed by the commits 3e5d316b72e3965b7968bb1d96baa137cd063ac6 and 643b24dbd002.
How can I determine whether a build is vulnerable?
Review whether the build includes the two listed fixing commits. The provided test case invokes Ghostscript with -dSAFER and attempts to use /OutputFile (%pipe%id); successful pipe execution indicates the unsafe state can be reached.