exrcheck: use 64 bit integer math to prevent pointer overflows #930
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Address issues:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31221
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31228
(also, all example images read through
exrcheck
when compiled with the undefined behavior sanitizer)exrcheck had the usual thorny bugs handling images with massively offset data windows. Where dataWindow.min.{x,y} are very large or very negative, 32 bit integer arithmetic overflows and/or negative pointer arithmetic occurred.
Signed-off-by: Peter Hillman peterh@wetafx.co.nz