From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: ghostscript vulnerabilities
Date: Wed, 12 Oct 2016 12:20:39 -0400 [thread overview]
Message-ID: <20161012162039.GA31608@jasmine> (raw)
In-Reply-To: <87insx37ss.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
On Wed, Oct 12, 2016 at 11:29:07PM +0800, Alex Vong wrote:
> > 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?
I don't know the relationship between GNU Ghostscript and "upstream"
Ghostscript. Can anyone explain why GNU offers its own distribution?
We can try cherry-picking the upstream commits that fix each of these
bugs [0]. Hopefully they apply to our older Ghostscript version.
If the resulting package's ABI is compatible to our current package, we
can apply it with a graft on the master branch.
We should also apply these patches to the ghostscript package on
core-updates.
Do you want to try it?
Debian helpfully links to the upstream commits corresponding to each
bug:
https://security-tracker.debian.org/tracker/CVE-2013-5653
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-12 16:20 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161012162039.GA31608@jasmine \
--to=leo@famulari.name \
--cc=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 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.