#34 Segmentation Fault (121467906)

[Google-Autofuzz]

Hello InChI team,

As part of our fuzzing efforts at Google, we have identified an issue affecting
InChI (tested with revision v1.04, September 2011).

To reproduce, we are attaching a Dockerfile which compiles the project with
LLVM, taking advantage of the sanitizers that it offers. More information about
how to use the attached Dockerfile can be found here:
https://docs.docker.com/engine/reference/builder/

Instructions:
unzip artifacts_121467906.zip
docker build --build-arg SANITIZER=address --tag=autofuzz-InChI-121467906 autofuzz_121467906
docker run --entrypoint /fuzzing/repro.sh --cap-add=SYS_PTRACE -v $PWD/autofuzz_121467906/poc-f41d0315cc426de09af02ebfd43ab7733a1bac17cb1c683630e09db394d23903_min:/tmp/poc autofuzz-InChI-121467906 "" /tmp/poc
docker run --cap-add=SYS_PTRACE -v $PWD/autofuzz_121467906/poc-f41d0315cc426de09af02ebfd43ab7733a1bac17cb1c683630e09db394d23903_min:/tmp/poc -it autofuzz-InChI-121467906

Alternatively, and depending on the bug, you could use gcc, valgrind or other
instrumentation tools to aid in the investigation. The sanitizer error that we
encountered is here:

INFO: Seed: 967251872
INFO: Loaded 0 modules (0 guards): 
/fuzzing/fuzzer: Running 1 inputs 500 time(s) each.
Running: /tmp/poc-f41d0315cc426de09af02ebfd43ab7733a1bac17cb1c683630e09db394d23903
ASAN:DEADLYSIGNAL
=================================================================
==6==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000fff0 (pc 0x00000042a76f bp 0x00000000fff0 sp 0x7ffe3f43a140 T0)
==6==The signal is caused by a WRITE memory access.
    #0 0x42a76e in __asan::asan_free(void*, __sanitizer::BufferedStackTrace*, __asan::AllocType) (/fuzzing/fuzzer+0x42a76e)
    #1 0x4ddf1c in __interceptor_cfree.localalias.0 (/fuzzing/fuzzer+0x4ddf1c)
    #2 0x6b2cac in CountTautomerGroups /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichitaut.c:4161:9
    #3 0x60324a in Create_INChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichimake.c:3028:44
    #4 0x6fe754 in MakeOneInChIOutOfStrFromINChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr1.c:4411:14
    #5 0x6ce8a7 in RestoreAtomMakeBNS /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2633:15
    #6 0x6cfd48 in OneInChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2840:11
    #7 0x67e7fc in InChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:131:11
    #8 0x681407 in AllInchiToStructure /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:787:23
    #9 0x659c40 in ReadWriteInChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:929:23
    #10 0x543f6e in GetStructFromINCHI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/inchi_dll.c:2293:16
    #11 0x518759 in LLVMFuzzerTestOneInput /fuzzing/security-research-pocs/autofuzz/inchi_fuzzer.cc:27:3
    #12 0x523ede in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/fuzzing/fuzzer+0x523ede)
    #13 0x51903e in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/fuzzing/fuzzer+0x51903e)
    #14 0x51d547 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/fuzzing/fuzzer+0x51d547)
    #15 0x518d5b in main (/fuzzing/fuzzer+0x518d5b)
    #16 0x7f70a03972e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
    #17 0x41ff89 in _start (/fuzzing/fuzzer+0x41ff89)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/fuzzing/fuzzer+0x42a76e) in __asan::asan_free(void*, __sanitizer::BufferedStackTrace*, __asan::AllocType)
==6==ABORTING

We will gladly work with you so you can successfully confirm and reproduce this
issue. Do let us know if you have any feedback surrounding the documentation.

Once you have reproduced the issue, we'd appreciate to learn your expected
timeline for an update to be released. With any fix, please attribute the report
to "Google Autofuzz project".

We are also pleased to inform you that your project is eligible for inclusion to
the OSS-Fuzz project, which can provide additional continuous fuzzing, and
encourage you to investigate integration options.

Don't hesitate to let us know if you have any questions!

Google AutoFuzz Team