CVE-2016-7977: Infoleak
First published: Tue May 23 2017(Updated: )
Ghostscript before 9.21 might allow remote attackers to bypass the SAFER mode protection mechanism and consequently read arbitrary files via the use of the .libfile operator in a crafted postscript document.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Ghostscript | <=9.20 |
Remedy
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8abd22010eb4db0fb1b10e430d5f5d83e015ef70
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8abd22010eb4db0fb1b10e430d5f5d83e015ef70
- http://rhn.redhat.com/errata/RHSA-2017-0013.html
- http://rhn.redhat.com/errata/RHSA-2017-0014.html
- http://www.debian.org/security/2016/dsa-3691
- http://www.openwall.com/lists/oss-security/2016/09/29/28
- http://www.openwall.com/lists/oss-security/2016/10/05/15
- http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
- http://www.securityfocus.com/bid/95334
- https://bugs.ghostscript.com/show_bug.cgi?id=697169
- https://ghostscript.com/doc/9.21/History9.htm
- https://security.gentoo.org/glsa/201702-31
- http://git.ghostscript.com/?p=ghostpdl.git%3Ba=commitdiff%3Bh=8abd22010eb4db0fb1b10e430d5f5d83e015ef70
Frequently Asked Questions
What is the severity of CVE-2016-7977?
CVE-2016-7977 has been classified as a high severity vulnerability due to its ability to bypass protection mechanisms.
How do I fix CVE-2016-7977?
To fix CVE-2016-7977, you should update Ghostscript to version 9.21 or later.
What types of attacks are possible due to CVE-2016-7977?
Due to CVE-2016-7977, attackers can potentially read arbitrary files on the server by exploiting crafted postscript documents.
Which versions of Ghostscript are affected by CVE-2016-7977?
CVE-2016-7977 affects all versions of Ghostscript prior to 9.21.
Is there a workaround for CVE-2016-7977 until a fix is applied?
There is no documented effective workaround for CVE-2016-7977; updating to a safe version is the recommended approach.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/author
- agent/severity
- agent/weakness
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/artifex
- canonical/ghostscript
- version/ghostscript/9.20