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_122094700.zip
docker build --build-arg SANITIZER=address --tag=autofuzz-InChI-122094700 autofuzz_122094700
docker run --entrypoint /fuzzing/repro.sh --cap-add=SYS_PTRACE -v $PWD/autofuzz_122094700/poc-bd72d0ef8dd6bfa8e984d93909497cd2d1ad997de2059be0f66805e1084d7a84_min:/tmp/poc autofuzz-InChI-122094700 "" /tmp/poc
docker run --cap-add=SYS_PTRACE -v $PWD/autofuzz_122094700/poc-bd72d0ef8dd6bfa8e984d93909497cd2d1ad997de2059be0f66805e1084d7a84_min:/tmp/poc -it autofuzz-InChI-122094700
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: 1386362214
INFO: Loaded 0 modules (0 guards):
/fuzzing/fuzzer: Running 1 inputs 500 time(s) each.
Running: /tmp/poc-bd72d0ef8dd6bfa8e984d93909497cd2d1ad997de2059be0f66805e1084d7a84
ASAN:DEADLYSIGNAL
=================================================================
==6==ERROR: AddressSanitizer: SEGV on unknown address 0x6208d3b56da0 (pc 0x00000066b852 bp 0x7ffeaf403af0 sp 0x7ffeaf403aa0 T0)
==6==The signal is caused by a READ memory access.
#0 0x66b851 in CopySegment(tagINChI*, tagINChI*, int, int, int) /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:7865:27
#1 0x679685 in ParseSegmentSp3(char const*, int, tagINChI**, int*, int, int*) /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:5639:23
#2 0x668cd9 in ReadInChILine(tagOutputStream*, tagLine*, char**, int*, tagINChI* (*) [2], int (*) [2], tagRemovedAndExchangeableH (*) [2], int (*) [2][2], int*, int*, unsigned char*) /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:4602:19
#3 0x65b3f7 in InChILine2Data(tagOutputStream*, tagLine*, char**, int*, int*, tagINChI* (*) [2], int (*) [2], tagRemovedAndExchangeableH (*) [2], int (*) [2][2], int, int, unsigned long, int*, int*, unsigned char*) /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:2327:11
#4 0x658fa5 in ReadWriteInChI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:571:23
#5 0x53dd6b in GetINCHIfromINCHI /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/inchi_dll.c:1953:16
#6 0x518735 in LLVMFuzzerTestOneInput /fuzzing/security-research-pocs/autofuzz/inchi_fuzzer.cc:23:3
#7 0x523ede in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/fuzzing/fuzzer+0x523ede)
#8 0x51903e in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/fuzzing/fuzzer+0x51903e)
#9 0x51d547 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/fuzzing/fuzzer+0x51d547)
#10 0x518d5b in main (/fuzzing/fuzzer+0x518d5b)
#11 0x7f0f69d9a2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
#12 0x41ff89 in _start (/fuzzing/fuzzer+0x41ff89)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /fuzzing/INCHI-1-API/INCHI_API/inchi_dll/ichiread.c:7865:27 in CopySegment(tagINChI*, tagINChI*, int, int, int)
==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