From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libsndfile: security bump to version 1.0.28
Date: Fri, 28 Apr 2017 14:31:34 +0200 [thread overview]
Message-ID: <87tw58hfx5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170426115214.8152-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 26 Apr 2017 13:52:14 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes:
> CVE-2017-7585 - In libsndfile before 1.0.28, an error in the
> "flac_buffer_copy()" function (flac.c) can be exploited to cause a
> stack-based buffer overflow via a specially crafted FLAC file.
> CVE-2017-7586 - In libsndfile before 1.0.28, an error in the "header_read()"
> function (common.c) when handling ID3 tags can be exploited to cause a
> stack-based buffer overflow via a specially crafted FLAC file.
> CVE-2017-7741 - In libsndfile before 1.0.28, an error in the
> "flac_buffer_copy()" function (flac.c) can be exploited to cause a
> segmentation violation (with write memory access) via a specially crafted
> FLAC file during a resample attempt, a similar issue to CVE-2017-7585.
> CVE-2017-7742 - In libsndfile before 1.0.28, an error in the
> "flac_buffer_copy()" function (flac.c) can be exploited to cause a
> segmentation violation (with read memory access) via a specially crafted
> FLAC file during a resample attempt, a similar issue to CVE-2017-7585.
> Dop undocumented patch adjusting SUBDIRS in Makefile.in as it no longer
> applies. Instead pass --disable-full-suite to disable man pages,
> documentation and programs, as that was presumably the reason for the patch.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-04-28 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 11:52 [Buildroot] [PATCH] libsndfile: security bump to version 1.0.28 Peter Korsgaard
2017-04-27 8:15 ` Peter Korsgaard
2017-04-28 12:31 ` 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=87tw58hfx5.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