Bug 2091804 (CVE-2022-31650) - CVE-2022-31650 sox: a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a
Summary: CVE-2022-31650 sox: a floating-point exception in lsx_aiffstartwrite in aiff....
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2022-31650
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2094698 2094699 2094700
Blocks: 2091808
TreeView+ depends on / blocked
 
Reported: 2022-05-31 05:50 UTC by Sandipan Roy
Modified: 2022-07-01 12:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A heap-based buffer overflow vulnerability exists in a reachable assertion in the rate_init of the Sound Exchange sox library. A specially-crafted file can lead to a floating-point exception. This flaw allows an attacker to provide a malicious file to trigger this vulnerability.
Clone Of:
Environment:
Last Closed: 2022-06-08 10:50:16 UTC


Attachments (Terms of Use)

Description Sandipan Roy 2022-05-31 05:50:44 UTC
Hello, I was testing my new fuzzer and found two bugs: a reachable assertion in rate_init, rate.c:303 and a float point exception in lsx_aiffstartwrite.
environment

sox latest commit 42b3557e13e0fe01a83465b672d89faddbe65f49,
clang 12.0.1,
Ubuntu 21.10
step to reproduce

compile sox with CC=clang, CFLAGS="-fsanitize=address -g"
run command ./sox --single-threaded @@ -t aiff /dev/null

https://sourceforge.net/p/sox/bugs/360/

Comment 1 Sandipan Roy 2022-06-08 08:24:36 UTC
Created sox tracking bugs for this issue:

Affects: epel-8 [bug 2094698]
Affects: fedora-35 [bug 2094699]
Affects: fedora-36 [bug 2094700]

Comment 2 Product Security DevOps Team 2022-06-08 10:50:14 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-31650


Note You need to log in before you can comment on or make changes to this bug.