From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wavpack: add upstream security fixes
Date: Tue, 10 Apr 2018 22:50:28 +0200 [thread overview]
Message-ID: <871sfm4wh7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180227212652.18759-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 27 Feb 2018 22:26:52 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> CVE-2018-6767: A stack-based buffer over-read in the ParseRiffHeaderConfig
> function of cli/riff.c file of WavPack 5.1.0 allows a remote attacker to
> cause a denial-of-service attack or possibly have unspecified other impact
> via a maliciously crafted RF64 file.
> CVE-2018-7253: The ParseDsdiffHeaderConfig function of the cli/dsdiff.c file
> of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service
> (heap-based buffer over-read) or possibly overwrite the heap via a
> maliciously crafted DSDIFF file.
> CVE-2018-7254: The ParseCaffHeaderConfig function of the cli/caff.c file of
> WavPack 5.1.0 allows a remote attacker to cause a denial-of-service (global
> buffer over-read), or possibly trigger a buffer overflow or incorrect memory
> allocation, via a maliciously crafted CAF file.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-04-10 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 21:26 [Buildroot] [PATCH] wavpack: add upstream security fixes Peter Korsgaard
2018-02-28 8:14 ` Peter Korsgaard
2018-04-10 20:50 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 13:27 Peter Korsgaard
2018-05-21 15:47 ` Peter Korsgaard
2018-06-11 21:16 ` 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=871sfm4wh7.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