From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/vorbis-tools: add upstream security fixes for CVE-2014-96{38, 39, 40}
Date: Tue, 4 Feb 2020 23:19:56 +0100 [thread overview]
Message-ID: <20200204231956.43d1dd8e@windsurf> (raw)
In-Reply-To: <20200204151819.22175-1-peter@korsgaard.com>
On Tue, 4 Feb 2020 16:18:19 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes the following security vulnerabilities:
>
> - CVE-2014-9638: oggenc in vorbis-tools 1.4.0 allows remote attackers to
> cause a denial of service (divide-by-zero error and crash) via a WAV file
> with the number of channels set to zero.
>
> - CVE-2014-9639: Integer overflow in oggenc in vorbis-tools 1.4.0 allows
> remote attackers to cause a denial of service (crash) via a crafted number
> of channels in a WAV file, which triggers an out-of-bounds memory access.
>
> - CVE-2014-9640: oggenc/oggenc.c in vorbis-tools 1.4.0 allows remote
> attackers to cause a denial of service (out-of-bounds read) via a crafted
> raw file.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> ...count-of-channels-in-the-header-CVE-.patch | 88 +++++++++++++++++++
> ...-on-raw-file-close-reported-by-Hanno.patch | 55 ++++++++++++
> 2 files changed, 143 insertions(+)
> create mode 100644 package/vorbis-tools/0002-oggenc-validate-count-of-channels-in-the-header-CVE-.patch
> create mode 100644 package/vorbis-tools/0003-oggenc-fix-crash-on-raw-file-close-reported-by-Hanno.patch
Applied to master, thanks. Glad to see that the CVE tooling is useful :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-04 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:18 [Buildroot] [PATCH] package/vorbis-tools: add upstream security fixes for CVE-2014-96{38, 39, 40} Peter Korsgaard
2020-02-04 22:19 ` Thomas Petazzoni [this message]
2020-03-10 20:55 ` 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=20200204231956.43d1dd8e@windsurf \
--to=thomas.petazzoni@bootlin.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