#32 Segmentation Fault (121413238)

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

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: 2378021896
INFO: Loaded 0 modules (0 guards): 
/fuzzing/fuzzer: Running 1 inputs 500 time(s) each.
Running: /tmp/poc-b9584192bb8e28b29c431c1ec9df54aea4efe826b2eb733e27b17700b7af4c99
ASAN:DEADLYSIGNAL
=================================================================
==6==ERROR: AddressSanitizer: SEGV on unknown address 0x62100088518c (pc 0x0000006e8305 bp 0x7ffdbe824750 sp 0x7ffdbe8246d0 T0)
==6==The signal is caused by a WRITE memory access.
    #0 0x6e8304 in GetTgroupInfoFromInChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr1.c:634:36
    #1 0x702cab in RestoreAtomConnectionsSetStereo /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr2.c:187:16
    #2 0x6cfc97 in OneInChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr4.c:2827:11
    #3 0x67e7fc in InChI2Atom /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:131:11
    #4 0x681407 in AllInchiToStructure /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichirvr7.c:787:23
    #5 0x659c40 in ReadWriteInChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:929:23
    #6 0x543f6e in GetStructFromINCHI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/inchi_dll.c:2293:16
    #7 0x518759 in LLVMFuzzerTestOneInput /fuzzing/security-research-pocs/autofuzz/inchi_fuzzer.cc:27:3
    #8 0x523ede in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/fuzzing/fuzzer+0x523ede)
    #9 0x51903e in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/fuzzing/fuzzer+0x51903e)
    #10 0x51d547 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/fuzzing/fuzzer+0x51d547)
    #11 0x518d5b in main (/fuzzing/fuzzer+0x518d5b)
    #12 0x7fcb8dbaa2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
    #13 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:634:36 in GetTgroupInfoFromInChI
==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