Red Hat Bugzilla – Bug 128158
CAN-2004-0557 buffer overflows in sox
Last modified: 2014-03-16 22:46:48 EDT
I have found two buffer overflows in SoX. They occur when the sox
or play commands handle malicious .WAV files.
Versions 12.17.4, 12.17.3 and 12.17.2 are vulnerable to these
overflows. 12.17.1, 12.17 and 12.16 are some versions that are not.
SoX may not be the most security critical program, but it is possible
to exploit this. Some attack vectors are social engineering (I have
used play to play .WAV files from untrusted sources several times
before I found this), programs that use SoX to play data from the net
(examples include JiveAudio and vmail), and people who put play in
their mailcap files (so it plays sound files in MIME messages as
soon as the messages are opened). It is also interesting to note
that xmms can play .WAV files with this type of data just fine.
// Ulf Harnhammar
Debian Security Audit Project
Created attachment 102036 [details]
WAV file which will trigger a buffer overflow.
To trigger the buffer overflow, just run 'play buffy.wav' (I didn't name it, I
have no idea).
Created attachment 102037 [details]
Fix for these buffer overflows.
Low, it doesn't seem much if anything uses this (unless you're aware
Low as in 'don't-do-it', or low as in 'do-it-at-some-point'?
Also, embargo date?
low as in do-it-at-some-point, and right now it looks like July 28 is
the embargo date. The reporter is still sorting out upstream, so this
may be optimistic.
public - removing embargo
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.