#35 Segmentation Fault (122000973)

[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_122000973.zip
docker build --build-arg SANITIZER=address --tag=autofuzz-InChI-122000973 autofuzz_122000973
docker run --entrypoint /fuzzing/repro.sh --cap-add=SYS_PTRACE -v $PWD/autofuzz_122000973/poc-80492681a2174c7c9fa9ffc09fa613b44fb59ef6cc851fa3c7505231b6170443_min:/tmp/poc autofuzz-InChI-122000973 "" /tmp/poc
docker run --cap-add=SYS_PTRACE -v $PWD/autofuzz_122000973/poc-80492681a2174c7c9fa9ffc09fa613b44fb59ef6cc851fa3c7505231b6170443_min:/tmp/poc -it autofuzz-InChI-122000973

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: 2170435021
INFO: Loaded 0 modules (0 guards): 
/fuzzing/fuzzer: Running 1 inputs 500 time(s) each.
Running: /tmp/poc-80492681a2174c7c9fa9ffc09fa613b44fb59ef6cc851fa3c7505231b6170443
ASAN:DEADLYSIGNAL
=================================================================
==6==ERROR: AddressSanitizer: SEGV on unknown address 0x0008c001a002 (pc 0x0000006fa154 bp 0x7ffe15ba41c0 sp 0x7ffe15ba3f80 T0)
==6==The signal is caused by a READ memory access.
    #0 0x6fa153 in EvaluateChargeChanges /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr1.c:3673:37
    #1 0x6fb414 in RunBnsTestOnce /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr1.c:3801:16
    #2 0x718923 in EliminateChargeSeparationOnHeteroatoms /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr2.c:3214:23
    #3 0x6cdbdd in RunBnsRestore1 /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2416:11
    #4 0x6cf560 in RestoreAtomMakeBNS /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2770:11
    #5 0x6cfd48 in OneInChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2840:11
    #6 0x67e7fc in InChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:131:11
    #7 0x681407 in AllInchiToStructure /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:787:23
    #8 0x659c40 in ReadWriteInChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:929:23
    #9 0x543f6e in GetStructFromINCHI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/inchi_dll.c:2293:16
    #10 0x518759 in LLVMFuzzerTestOneInput /fuzzing/security-research-pocs/autofuzz/inchi_fuzzer.cc:27:3
    #11 0x523ede in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/fuzzing/fuzzer+0x523ede)
    #12 0x51903e in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/fuzzing/fuzzer+0x51903e)
    #13 0x51d547 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/fuzzing/fuzzer+0x51d547)
    #14 0x518d5b in main (/fuzzing/fuzzer+0x518d5b)
    #15 0x7f07d2c572e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
    #16 0x41ff89 in _start (/fuzzing/fuzzer+0x41ff89)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr1.c:3673:37 in EvaluateChargeChanges
==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