memory leaks detected

[fCorleone]

=================================================================
==11731==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 12736 byte(s) in 1 object(s) allocated from:
#0 0x7ffff6f0279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)
#1 0x7ffff6b3deb7 in psf_allocate src/common.c:45

Indirect leak of 3672 byte(s) in 1 object(s) allocated from:
#0 0x7ffff6f02961 in realloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98961)
#1 0x7ffff6b4fb24 in psf_bump_header_allocation src/common.c:70
#2 0x7ffff6b4fb24 in header_seek src/common.c:886
#3 0x7ffff6b4fb24 in psf_binheader_readf src/common.c:1121

Indirect leak of 1920 byte(s) in 1 object(s) allocated from:
#0 0x7ffff6f0279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)
#1 0x7ffff6bfe0a0 in psf_store_read_chunk src/chunk.c:114
#2 0x7ffff6bfe0a0 in psf_store_read_chunk_u32 src/chunk.c:151
#3 0x7ffff6c35117 (/usr/local/lib/libsndfile.so.1+0x260117)

Indirect leak of 528 byte(s) in 1 object(s) allocated from:
#0 0x7ffff6f0279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)
#1 0x7ffff6aaed7f in wav_open src/wav.c:163

Indirect leak of 256 byte(s) in 1 object(s) allocated from:
#0 0x7ffff6f02961 in realloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98961)
#1 0x7ffff6be8116 in psf_store_string src/strings.c:134
The command line is ./sndfile-convert ./2.wav ./out.prc where 2.wav is just a simple wav file.

[erikd]

What version of libsndfile is this? Is this, or have you tried current git HEAD?

It would also be useful for you to post the sndfile-info output for that file.

[carnil]

This issue was assigned CVE-2018-13419

[sgayou]

Unable to reproduce this on libsndfile-1.0.28 with a clang fsanitize=leak build. Seems like the convert operation will only complete with the input wav has a single channel. The wav file used to trigger the leak would be useful in addition to the lsan log.

./sndfile-convert -endian=little -alaw tone.wav test.prc

No dice in valgrind either. Let me know if anyone else has more success.

[abergmann]

@fCorleone any chance to publish the reproducer here? Thanks!

[erikd]

Closing this for now. If a file can be provided that triggers this issue please feel free to re-open.