https://seclists.org/oss-sec/2018/q3/229

Published Sep 9, 2018
·
Updated

Affected Software

1 affected component
Artifex ghostscript

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203