From: "Jaromír Mikeš" <mira.mikes@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Re: [PATCH] aiff: fix crash on empty comment chunk (CVE-2017-15642)
Date: Mon, 20 Nov 2017 13:22:55 +0100 [thread overview]
Message-ID: <CAG_ZyaCVvKtwoXV+fTOBQohb8F9LDpUwwECG7XbJboqZ9VXgDA@mail.gmail.com> (raw)
In-Reply-To: <20171120110535.14410-1-mans@mansr.com>
[-- Attachment #1.1: Type: text/plain, Size: 1403 bytes --]
2017-11-20 12:05 GMT+01:00 Mans Rullgard <mans@mansr.com>:
> This fixes a use after free and double free if an empty comment
> chunk follows a non-empty one.
> ---
> src/aiff.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/aiff.c b/src/aiff.c
> index e34286be0a97..197ccd4e5d20 100644
> --- a/src/aiff.c
> +++ b/src/aiff.c
> @@ -63,7 +63,6 @@ int lsx_aiffstartread(sox_format_t * ft)
> size_t ssndsize = 0;
> char *annotation;
> char *author;
> - char *comment = NULL;
> char *copyright;
> char *nametext;
>
> @@ -271,6 +270,7 @@ int lsx_aiffstartread(sox_format_t * ft)
> free(annotation);
> }
> else if (strncmp(buf, "COMT", (size_t)4) == 0) {
> + char *comment = NULL;
> rc = commentChunk(&comment, "Comment:", ft);
> if (rc) {
>>
>> 2.15.0
>
>
>>
>>
>> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
>
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> _______________________________________________
>
> SoX-devel mailing list
>
> SoX-devel@lists.sourceforge.net
>
> https://lists.sourceforge.net/lists/listinfo/sox-devel
>
> /* Fail already called in function */
> --
>
Thank you! Applied in debian repo.
best regards
mira
[-- Attachment #1.2: Type: text/html, Size: 3681 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2017-11-20 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 9:17 New CVE bug Jaromír Mikeš
2017-11-20 11:05 ` [PATCH] aiff: fix crash on empty comment chunk (CVE-2017-15642) Mans Rullgard
2017-11-20 12:22 ` Jaromír Mikeš [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG_ZyaCVvKtwoXV+fTOBQohb8F9LDpUwwECG7XbJboqZ9VXgDA@mail.gmail.com \
--to=sox-devel@lists.sourceforge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).