Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divide by Zero at calculateNumTiles (72239767) #266

Closed
Google-Autofuzz opened this issue Feb 13, 2018 · 0 comments · Fixed by #442
Closed

Divide by Zero at calculateNumTiles (72239767) #266

Google-Autofuzz opened this issue Feb 13, 2018 · 0 comments · Fixed by #442
Labels
Bug A bug in the source code

Comments

@Google-Autofuzz
Copy link

Hello OpenEXR team,

As part of our fuzzing efforts at Google, we have identified an issue affecting
OpenEXR (tested with revision * develop 165dcea).

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 project
  • cp Dockerfile.OpenEXR /path/to/project/Dockerfile
  • docker build --no-cache /path/to/project
  • docker run -it image_id_from_docker_build

From 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:

INFO: Seed: 3939730443
/fuzzing/fuzzer: Running 1 inputs 1 time(s) each.
Running: /tmp/poc
ImfTiledMisc.cpp:304:60: runtime error: division by zero
SUMMARY: AddressSanitizer: undefined-behavior ImfTiledMisc.cpp:304:60 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
artifacts_72239767.zip

@cary-ilm cary-ilm added the Bug A bug in the source code label Jun 13, 2019
peterhillman added a commit to peterhillman/openexr that referenced this issue Jul 15, 2019
…r unknown tiled types. Enforce for both InputFile and InputPart API. Fixes AcademySoftwareFoundation#266, Related to AcademySoftwareFoundation#70
peterhillman added a commit that referenced this issue Jul 16, 2019
…r unknown tiled types. Enforce for both InputFile and InputPart API. Fixes #266, Related to #70
DominicJacksonBFX pushed a commit to boris-fx/mocha-openexr that referenced this issue Jun 22, 2022
…r unknown tiled types. Enforce for both InputFile and InputPart API. Fixes AcademySoftwareFoundation#266, Related to AcademySoftwareFoundation#70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug in the source code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants