First published: Thu Jan 05 2012(Updated: )
Ghostscript included the current working directory in its library search path by default. If a user ran Ghostscript without the "-P-" option in an attacker-controlled directory containing a specially-crafted PostScript library file, it could cause Ghostscript to execute arbitrary PostScript code. With this update, Ghostscript no longer searches the current working directory for library files by default. (<a href="https://access.redhat.com/security/cve/CVE-2010-4820">CVE-2010-4820</a>) Note: The fix for <a href="https://access.redhat.com/security/cve/CVE-2010-4820">CVE-2010-4820</a> could possibly break existing configurations. To use the previous, vulnerable behavior, run Ghostscript with the "-P" option (to always search the current working directory first).
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Artifex Ghostscript | =8.62 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4820 has been classified as a medium severity vulnerability due to the potential for arbitrary code execution.
To fix CVE-2010-4820, it is recommended to run Ghostscript with the "-P-" option or update to a patched version of Ghostscript.
CVE-2010-4820 affects Ghostscript version 8.62.
CVE-2010-4820 allows an attacker to execute arbitrary PostScript code by placing a specially-crafted library file in a controlled directory.
Running Ghostscript with default settings is unsafe if the current working directory is controlled by an attacker, due to CVE-2010-4820.