all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Didier Link <didier@famille-link.fr>
To: bug-ghostscript@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: ghostscript vulnerabilities
Date: Sun, 6 Nov 2016 19:34:55 +0100	[thread overview]
Message-ID: <85f3d7fe-56e2-be63-3595-929e928220ed@famille-link.fr> (raw)
In-Reply-To: <87twcc5m90.fsf@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2908 bytes --]

Le 16/10/2016 à 17:47, Alex Vong a écrit :
> Hello,
>
> I notice the patch for CVE-2016-7977[0] handles the problem differently
> than GNU Ghostscript[1] does. Maybe you can take a look at it.
>
> [0]: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8abd22010eb4db0fb1b10e430d5f5d83e015ef70
> [1]: http://git.savannah.gnu.org/cgit/ghostscript.git/tree/psi/zfile.c
>
> Thanks,
> Alex

Hello,

I've just released a gnu-ghostscript point release with the CVE patches
adapted by Mark (really thanks !!!).

For the CVE-2016-7977 I've see that the file concerned was modified in
later release of gpl-ghostscript, I will see in later release of gnu
version ;)

Best regards

Didier

>
> Didier Link <didier@famille-link.fr> writes:
>
>> Hello all
>>
>> I will review the Mark's patches and apply them for a security release next week.
>>
>> Thanks for your help !
>>
>> Best regards
>>
>> Didier
>>
>> Le 15/10/2016 à 09:36, Mark H Weaver a écrit :
>>
>>  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



[-- Attachment #1.1.2: Type: text/html, Size: 4660 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2016-11-06 18:35 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
2016-10-16  9:16       ` Didier Link
2016-10-16 15:47         ` Alex Vong
2016-11-06 18:34           ` Didier Link [this message]
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=85f3d7fe-56e2-be63-3595-929e928220ed@famille-link.fr \
    --to=didier@famille-link.fr \
    --cc=bug-ghostscript@gnu.org \
    --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.