Heap Out-of-Bounds Write in SoX Audio Processor

Executive Summary

This vulnerability is a heap out-of-bounds write flaw in SoX through version 14.4.2. It occurs in the MS ADPCM WAV decoding function lsx_ms_adpcm_block_expand_i() when an odd samplesPerBlock value is present in the WAV fmt chunk. Attackers can exploit this by providing a crafted MS ADPCM WAV file to sox or any libsox consumer, causing a partially controlled 16-bit sample to be written past the allocated heap buffer.

Useful 0 Not Useful 0

Detection Guidance

To detect this vulnerability, inspect WAV files processed by SoX or libsox for odd samplesPerBlock values in the fmt chunk. Use tools like hexdump or a hex editor to examine the WAV header. Run SoX with AddressSanitizer or Valgrind to detect heap out-of-bounds writes during file processing.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability may cause crashes under hardened allocators or tools like AddressSanitizer due to heap corruption. While it does not directly enable code execution or information leaks, it could lead to denial of service or instability in applications using vulnerable versions of SoX or libsox.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability primarily causes heap corruption through a buffer overflow, which may lead to crashes or instability in applications using libsox. It does not directly enable code execution or information leaks, limiting its immediate impact on compliance with standards like GDPR or HIPAA. However, if exploited to cause denial of service in systems handling sensitive data, it could indirectly affect availability requirements under these regulations.

Useful 0 Not Useful 0

Mitigation Strategies

Immediately update SoX to the latest patched version. If updating is not possible, avoid processing untrusted WAV files, especially MS ADPCM encoded files. Implement input validation to reject WAV files with odd samplesPerBlock values. Use sandboxing or hardened allocators to limit exploitability.

Useful 0 Not Useful 0