-
Notifications
You must be signed in to change notification settings - Fork 629
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
AddressSanitizer CHECK failed in ImageMagick fuzz test. #213
Comments
That doesn't look like a memory allocation failure to me. The OpenEXR code involved looks sound: when reading the input, which I assume is a fuzzed file, the flags in the header aren't recognized, so a C++ exception is thrown. The 'CHECK failed' message looks like internal confusion of AddressSanitizer. How is this built? What platform, compiler, etc? ImageMagick, written in C, is calling OpenEXR via a shim layer provided by OpenEXR that wraps its normal C++ API, which, among other things, puts functions inside a try/catch and using a different means of reporting errors back to the caller. That should all be sound, but perhaps something about the way the program under test is compiled and linked causes it to be missing code to handle C++ exceptions that is needed here. |
You are right. This is not a problem with the memory. I'm sorry, I got confused fro another thing. Openexr here is built from portage (the gentoo package manager) so from source. The compiler is gcc-4.9.3 on x86_64 |
Looking into the OpenEXR issue backlog. Is this still reproducible? Is there any further information? |
Closing the issue for now, feel free to re-open or file a new issue if you need further help. |
During the fuzz of imagemagick I noticed a memory allocation failure in openexr.
Testcase: https://github.com/asarubbo/poc/blob/master/00033-openexr-memalloc-ImfGenericInputFile_cpp
The text was updated successfully, but these errors were encountered: