unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/2] OpenJPEG security fixes (CVE-2016-{5157,7163})
Date: Fri,  9 Sep 2016 02:04:39 -0400	[thread overview]
Message-ID: <cover.1473400918.git.leo@famulari.name> (raw)

Two bugs disclosed in OpenJPEG, CVE-2016-5157 and CVE-2016-7163. Both
can be used to execute arbitrary code, apparently.

CVE-2016-7163:
http://seclists.org/oss-sec/2016/q3/442

CVE-2016-5157:
http://seclists.org/oss-sec/2016/q3/441

Leo Famulari (2):
  gnu: openjpeg-2.*: Fix CVE-2016-7163.
  gnu: openjpeg-2.*: Fix CVE-2016-5157.

 gnu/local.mk                                      |  2 +
 gnu/packages/image.scm                            |  8 +-
 gnu/packages/patches/openjpeg-CVE-2016-5157.patch | 98 +++++++++++++++++++++++
 gnu/packages/patches/openjpeg-CVE-2016-7163.patch | 71 ++++++++++++++++
 4 files changed, 177 insertions(+), 2 deletions(-)
 create mode 100644 gnu/packages/patches/openjpeg-CVE-2016-5157.patch
 create mode 100644 gnu/packages/patches/openjpeg-CVE-2016-7163.patch

-- 
2.10.0

             reply	other threads:[~2016-09-09  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09  6:04 Leo Famulari [this message]
2016-09-09  6:04 ` [PATCH 1/2] gnu: openjpeg-2.*: Fix CVE-2016-7163 Leo Famulari
2016-09-09  7:15   ` Efraim Flashner
2016-09-09  7:59     ` Leo Famulari
2016-09-09 22:29       ` Ludovic Courtès
2016-09-09  6:04 ` [PATCH 2/2] gnu: openjpeg-2.*: Fix CVE-2016-5157 Leo Famulari
2016-09-09  8:09   ` Leo Famulari
2016-09-09  7:16 ` [PATCH 0/2] OpenJPEG security fixes (CVE-2016-{5157,7163}) Efraim Flashner
2016-09-09 18:04 ` v2: " Leo Famulari
2016-09-09 20:26   ` Leo Famulari
2016-09-09 22:34     ` Ludovic Courtès
2016-09-10  1:05       ` Leo Famulari

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=cover.1473400918.git.leo@famulari.name \
    --to=leo@famulari.name \
    --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).