Hello International Chemical Identifier (InChI) team,
As part of our fuzzing efforts at Google, we have identified an issue affecting
International Chemical Identifier (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/
TL;DR instructions:
mkdir projectcp Dockerfile /path/to/projectdocker build --no-cache /path/to/projectdocker run -it image_id_from_docker_buildFrom another terminal, outside the container:
docker cp /path/to/attached/reproducer running_container_hostname:/fuzzing/reproducer
(reference: https://docs.docker.com/engine/reference/commandline/cp/)
And, back inside the container:
/fuzzing/repro.sh /fuzzing/reproducer
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:
ichiprt2.c:1524:17: runtime error: signed integer overflow: 2966846567891779131 * 27 cannot be represented in type 'long'
SUMMARY: AddressSanitizer: undefined-behavior ichiprt2.c:1524:17 in
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
68417098