From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libsndfile: add upstream post-1.0.28 security fixes
Date: Sat, 19 Jan 2019 16:33:38 +0100 [thread overview]
Message-ID: <87pnss3bn1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190118085518.7729-1-peter@korsgaard.com> (Peter Korsgaard's message of "Fri, 18 Jan 2019 09:55:18 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security vulnerabilities:
> CVE-2017-14634: In libsndfile 1.0.28, a divide-by-zero error exists in the
> function double64_init() in double64.c, which may lead to DoS when playing a
> crafted audio file
> CVE-2017-17456: The function d2alaw_array() in alaw.c of libsndfile
> 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown address
> 0x000000000000), a different vulnerability than CVE-2017-14245
> CVE-2017-17457: The function d2ulaw_array() in ulaw.c of libsndfile
> 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown address
> 0x000000000000), a different vulnerability than CVE-2017-14246
> CVE-2018-13139: A stack-based buffer overflow in psf_memset in common.c in
> libsndfile 1.0.28 allows remote attackers to cause a denial of service
> (application crash) or possibly have unspecified other impact via a crafted
> audio file. The vulnerability can be triggered by the executable
> sndfile-deinterleave
> CVE-2018-19661: An issue was discovered in libsndfile 1.0.28. There is a
> buffer over-read in the function i2ulaw_array in ulaw.c that will lead to a
> denial of service
> CVE-2018-19662: An issue was discovered in libsndfile 1.0.28. There is a
> buffer over-read in the function i2alaw_array in alaw.c that will lead to a
> denial of service
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-01-19 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 8:55 [Buildroot] [PATCH] package/libsndfile: add upstream post-1.0.28 security fixes Peter Korsgaard
2019-01-19 15:33 ` Peter Korsgaard [this message]
2019-01-29 16:11 ` 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=87pnss3bn1.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