Numeric truncation at tif_dirread.c:4386#23986
Merged
asmorkalov merged 1 commit intoopencv:4.xfrom Jul 27, 2023
Merged
Conversation
Contributor
|
OpenCV team usually does not accept patches for 3rdparty components. Could you send the patch to original repo. The fix will be promoted to OpenCV after TIFF release. |
Contributor
Author
I've sent merge request to libtiff. |
Contributor
Author
|
@asmorkalov @opencv-alalek Hi! Fix in LibTIFF was merged. |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi! We've been fuzzing opencv with sydr-fuzz security predicates and we found numeric truncation error in
tif_dirread.c:4386.In function
TIFFReadDirectoryCheckOrderon line 4386 variablemhas typeuint16, structureTIFFDirEntryhas fielduint16 tdir_tag. But on the right side of operator there is an integer type value (due to the integer promotion), so the numeric truncation may occur. Our tool has found input wheno->tdir_tagis equal to 65535 (uint16_max), so then valueo->tdir_tag+1truncates to zero in variablem. Thenmis used in if operator on line 4380, and it is obvious, thato->tdir_tag<mcan't be true after truncation and the break from the cycle will not occur even with not ascending order of tags. So we suggest to change the typeint16_tof the variablemto typeuint32.Environment
How to reproduce this error
Build docker container:
Run docker container:
Run on the following input:
Output: