From: Alex Vong <alexvong1995@gmail.com>
To: guix-devel@gnu.org
Subject: ghostscript vulnerabilities
Date: Wed, 12 Oct 2016 23:29:07 +0800 [thread overview]
Message-ID: <87insx37ss.fsf@gmail.com> (raw)
In-Reply-To: <E1buKjg-00057S-2V@master.debian.org> (Salvatore Bonaccorso's message of "Wed, 12 Oct 2016 14:42:24 +0000")
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Hello,
Below are from the security announcement list:
Salvatore Bonaccorso <carnil@debian.org> writes:
> -------------------------------------------------------------------------
> Debian Security Advisory DSA-3691-1 security@debian.org
> https://www.debian.org/security/ Salvatore Bonaccorso
> October 12, 2016 https://www.debian.org/security/faq
> -------------------------------------------------------------------------
>
> Package : ghostscript
> CVE ID : CVE-2013-5653 CVE-2016-7976 CVE-2016-7977 CVE-2016-7978
> CVE-2016-7979 CVE-2016-8602
> Debian Bug : 839118 839260 839841 839845 839846 840451
>
> Several vulnerabilities were discovered in Ghostscript, the GPL
> PostScript/PDF interpreter, which may lead to the execution of arbitrary
> code or information disclosure if a specially crafted Postscript file is
> processed.
>
> For the stable distribution (jessie), these problems have been fixed in
> version 9.06~dfsg-2+deb8u3.
>
> We recommend that you upgrade your ghostscript packages.
>
> Further information about Debian Security Advisories, how to apply
> these updates to your system and frequently asked questions can be
> found at: https://www.debian.org/security/
>
> Mailing list: debian-security-announce@lists.debian.org
I've checked just now. GNU Ghostscript is also affected at least by
CVE-2016-8602. Looking at the patch in this bug report[0] and the
source[1], one can see that the vulnerable lines are present in GNU
Ghostscript. What should we do now?
[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840451
[1]: http://git.savannah.gnu.org/cgit/ghostscript.git/tree/psi/zht2.c
Thanks,
Alex
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next parent reply other threads:[~2016-10-12 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1buKjg-00057S-2V@master.debian.org>
2016-10-12 15:29 ` Alex Vong [this message]
2016-10-12 16:20 ` ghostscript vulnerabilities Leo Famulari
2016-10-12 16:26 ` Leo Famulari
2016-10-12 21:13 ` Ludovic Courtès
2016-10-15 7:36 ` Mark H Weaver
2016-10-16 9:16 ` Didier Link
2016-10-16 15:47 ` Alex Vong
2016-11-06 18:34 ` Didier Link
2016-11-06 21:38 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87insx37ss.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).