Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lame: security bump to version 3.100
Date: Wed, 25 Oct 2017 09:41:46 +0200	[thread overview]
Message-ID: <871slr65dx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171022111508.5361-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sun, 22 Oct 2017 13:15:08 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issues:
 > CVE-2017-9410: fill_buffer_resample function in libmp3lame/util.c heap-based
 > buffer over-read and ap

 > CVE-2017-9411: fill_buffer_resample function in libmp3lame/util.c invalid
 > memory read and application crash

 > CVE-2017-9412: unpack_read_samples function in frontend/get_audio.c invalid
 > memory read and application crash

 > Drop patches now upstream or no longer needed:

 > 0001-configure.patch: Upstream as mentioned in patch description

 > 0002-gtk1-ac-directives.patch: Upstream as mentioned in patch
 > description/release notes:

 > Resurrect Owen Taylor's code dated from 97-11-3 to properly deal with GTK1.
 > This was transplanted back from aclocal.m4 with a patch provided by Andres
 > Mejia. This change makes it easy to regenerate autotools' files with a simple
 > invocation of autoconf -vfi.

 > 0003-msse.patch: Not needed as -march <x86-variant-with-msse-support>
 > nowadays implies -msse.

 > With these removed, autoreconf is no longer needed.

 > Also add a hash for the license file while we're at it.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-10-25  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 11:15 [Buildroot] [PATCH] lame: security bump to version 3.100 Peter Korsgaard
2017-10-22 12:05 ` Thomas Petazzoni
2017-10-22 22:49 ` Peter Korsgaard
2017-10-25  7:41 ` Peter Korsgaard [this message]

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=871slr65dx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox