From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wavpack: add upstream security fixes
Date: Mon, 21 May 2018 17:47:18 +0200 [thread overview]
Message-ID: <87a7stj9ix.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180521132720.17915-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 21 May 2018 15:27:20 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> CVE-2018-10536: An issue was discovered in WavPack 5.1.0 and earlier. The
> WAV parser component contains a vulnerability that allows writing to memory
> because ParseRiffHeaderConfig in riff.c does not reject multiple format
> chunks.
> CVE-2018-10537: An issue was discovered in WavPack 5.1.0 and earlier. The
> W64 parser component contains a vulnerability that allows writing to memory
> because ParseWave64HeaderConfig in wave64.c does not reject multiple format
> chunks.
> CVE-2018-10538: An issue was discovered in WavPack 5.1.0 and earlier for WAV
> input. Out-of-bounds writes can occur because ParseRiffHeaderConfig in
> riff.c does not validate the sizes of unknown chunks before attempting
> memory allocation, related to a lack of integer-overflow protection within a
> bytes_to_copy calculation and subsequent malloc call, leading to
> insufficient memory allocation.
> CVE-2018-10539: An issue was discovered in WavPack 5.1.0 and earlier for
> DSDiff input. Out-of-bounds writes can occur because
> ParseDsdiffHeaderConfig in dsdiff.c does not validate the sizes of unknown
> chunks before attempting memory allocation, related to a lack of
> integer-overflow protection within a bytes_to_copy calculation and
> subsequent malloc call, leading to insufficient memory allocation.
> CVE-2018-10540: An issue was discovered in WavPack 5.1.0 and earlier for W64
> input. Out-of-bounds writes can occur because ParseWave64HeaderConfig in
> wave64.c does not validate the sizes of unknown chunks before attempting
> memory allocation, related to a lack of integer-overflow protection within a
> bytes_to_copy calculation and subsequent malloc call, leading to
> insufficient memory allocation.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-21 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 13:27 [Buildroot] [PATCH] wavpack: add upstream security fixes Peter Korsgaard
2018-05-21 15:47 ` Peter Korsgaard [this message]
2018-06-11 21:16 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2018-02-27 21:26 Peter Korsgaard
2018-02-28 8:14 ` Peter Korsgaard
2018-04-10 20:50 ` 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=87a7stj9ix.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