From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: didier@famille-link.fr, guix-devel@gnu.org, bug-ghostscript@gnu.org
Subject: Re: ghostscript vulnerabilities
Date: Sat, 15 Oct 2016 03:36:45 -0400 [thread overview]
Message-ID: <87a8e6jc6q.fsf@netris.org> (raw)
In-Reply-To: <87mvi9l17x.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 12 Oct 2016 23:13:54 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello Didier and all,
>
> We are wondering about the applicability to GNU Ghostscript of the
> recent vulnerabilities discovered in AGPL Ghostscript:
>
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> 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.
>
> [...]
>
>> 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
>
> WDYT? Perhaps a new release incorporating the fixes is in order?
FYI, I ported the upstream patches to GNU ghostscript for GNU Guix.
You can find them here:
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=1de17a648fa631f0074d315bfff0716220ce4880
Mark
next prev parent reply other threads:[~2016-10-15 7:37 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 ` ghostscript vulnerabilities Alex Vong
2016-10-12 16:20 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8e6jc6q.fsf@netris.org \
--to=mhw@netris.org \
--cc=bug-ghostscript@gnu.org \
--cc=didier@famille-link.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.