From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libvorbis: add upstream security fixes
Date: Sun, 18 Feb 2018 21:56:23 +0100 [thread overview]
Message-ID: <871shikoeg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180216080955.21114-1-peter@korsgaard.com> (Peter Korsgaard's message of "Fri, 16 Feb 2018 09:09:55 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> CVE-2017-14632: Libvorbis 1.3.5 allows Remote Code Execution upon freeing
> uninitialized memory in the function vorbis_analysis_headerout() in info.c
> when vi->channels<=0, a similar issue to Mozilla bug 550184.
> CVE-2017-14633: In libvorbis 1.3.5, an out-of-bounds array read
> vulnerability exists in the function mapping0_forward() in mapping0.c, which
> may lead to DoS when operating on a crafted audio file with
> vorbis_analysis().
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-18 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 8:09 [Buildroot] [PATCH] libvorbis: add upstream security fixes Peter Korsgaard
2018-02-18 20:56 ` Peter Korsgaard [this message]
2018-04-10 20:46 ` Peter Korsgaard
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=871shikoeg.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