From: Martin Guy <martinwguy@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Fwd: CVE-2019-8354 claims to have been fixed in SoX, but isn't
Date: Thu, 30 May 2024 12:59:25 +0200 [thread overview]
Message-ID: <bb027977-7fcc-4afe-bcc0-d7228f93b6a2@gmail.com> (raw)
In-Reply-To: <8e47e777-8f18-4c93-8f93-22aa08505c64@gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1724 bytes --]
-------- Forwarded Message --------
Subject: CVE-2019-8354 claims to have been fixed in SoX, but isn't
Date: Thu, 30 May 2024 12:49:17 +0200
From: Martin Guy <martinwguy@gmail.com>
To: nvd@NIST.gov
https://nvd.nist.gov/vuln/detail/CVE-2019-8354
claims to have been fixed on Apr 24 14:57:34 2019 +0100 in the SoX
commit logs:
fix possible buffer size overflow in lsx_make_lpf() (CVE-2019-8354)
The multiplication in the size argument malloc() might overflow,
resulting in a small buffer being allocated. Use calloc() instead.
but the segmentation fault (core dumped) persists both immediately after
this commit and in all subsequent versions:
Repeat-by:
sox --single-threaded crash_effect_i_dsp_c_367_heap_buffer_overflow.mp3
-t aiff /dev/null channels 1 rate 16k fade 3 norm
sox: effects_i_dsp.c:188: update_fft_cache: Assertion
`lsx_is_power_of_2(len)' failed.
Aborted (core dumped)
gdb src/.libs/sox core
Program terminated with signal SIGABRT, Aborted.
#0 0xb7f0b559 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7f0b559 in __kernel_vsyscall ()
#1 0xb7b9e2e7 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2 0xb7b4d111 in raise () from /lib/i386-linux-gnu/libc.so.6
#3 0xb7b3626a in abort () from /lib/i386-linux-gnu/libc.so.6
#4 0xb7b3616c in ?? () from /lib/i386-linux-gnu/libc.so.6
#5 0xb7b45689 in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
#6 0xb7e82a73 in update_fft_cache (len=len@entry=0) at effects_i_dsp.c:188
where crash_effect_i_dsp_c_367_heap_buffer_overflow.mp3 is attached to
https://sourceforge.net/p/sox/bugs/319/
and here.
Thanks and keep up the good work
M
[-- Attachment #1.1.1.2: crash_effect_i_dsp_c_367_heap_buffer_overflow.mp3 --]
[-- Type: audio/mpeg, Size: 1352 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- 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
next parent reply other threads:[~2024-05-30 10:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e47e777-8f18-4c93-8f93-22aa08505c64@gmail.com>
2024-05-30 10:59 ` Martin Guy [this message]
2024-05-30 13:48 ` Fwd: CVE-2019-8354 claims to have been fixed in SoX, but isn't Måns Rullgård
2024-05-30 15:44 ` Martin Guy
2024-05-30 17:14 ` Måns Rullgård
2024-06-01 9:31 ` Fwd: CVE-2019-8354 Jan Stary
2024-06-01 10:36 ` Martin Guy
2024-06-01 11:24 ` Jan Stary
2024-06-01 13:29 ` Martin Guy
2024-06-01 13:55 ` Jan Stary
2024-06-01 19:23 ` Martin Guy
2024-05-31 9:17 ` Fwd: CVE-2019-8354 claims to have been fixed in SoX, but isn't Jan Stary
2024-06-01 9:27 ` SoX malloc (was Re: Fwd: CVE-2019-8354) Jan Stary
2024-06-01 9:38 ` Jan Stary
2024-06-01 11:26 ` Jan Stary
2024-06-01 13:11 ` Jan Stary
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=bb027977-7fcc-4afe-bcc0-d7228f93b6a2@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).