Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEGV signal found when running aubiomfcc #187

Closed
fCorleone opened this issue Jul 22, 2018 · 3 comments
Closed

SEGV signal found when running aubiomfcc #187

fCorleone opened this issue Jul 22, 2018 · 3 comments
Labels

Comments

@fCorleone
Copy link

I was running aubiomfcc with a wav file as an input and I got a crash . The address sanitizer reported as:

=================================================================
==12014==ERROR: AddressSanitizer: SEGV on unknown address 0x000000003a50 (pc 0x7f51b0a74d44 bp 0x00000000003e sp 0x7fff2e4b6290 T0)

    #0 0x7f51b0a74d43 in swr_is_initialized (/usr/lib/x86_64-linux-gnu/libswresample-ffmpeg.so.1+0xdd43)
    #1 0x7f51b0a74da7 in swr_convert (/usr/lib/x86_64-linux-gnu/libswresample-ffmpeg.so.1+0xdda7)
    #2 0x7f51b344871b in aubio_source_avcodec_readframe ../src/io/source_avcodec.c:439
    #3 0x7f51b344934b in aubio_source_avcodec_do ../src/io/source_avcodec.c:476
    #4 0x405799 in examples_common_process ../examples/utils.c:168
    #5 0x404bde in main ../examples/aubiomfcc.c:71
    #6 0x7f51b307b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
    #7 0x401668 in _start (/home/mfc_fuzz/aubio/build/dist/usr/local/bin/aubiomfcc+0x401668)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ??:0 swr_is_initialized
==12014==ABORTING

The input file I give to the program is displayed at: https://github.com/fCorleone/fuzz_programs/blob/master/aubio/testcase1
The command line is just ./aubiomfcc -i testcase1

@piem
Copy link
Member

piem commented Aug 6, 2018

hi @fCorleone

great, thanks for the fuzz reports! i will look into them.

cheers, piem

@piem
Copy link
Member

piem commented Aug 6, 2018

I believe this is a duplicate of the first test case in #137 (not #148, sorry for the noise), which is fixed with the above patch.

cheers, piem

@piem piem added the security label Aug 6, 2018
@piem
Copy link
Member

piem commented Aug 6, 2018

The patch is at a81b12a in branch fix/avr_context.

@piem piem closed this as completed in a81b12a Aug 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants