enforce limit on area of deep tiles to prevent excessive memory use #939
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.
This change enforces a hard limit on deep tile sizes, so that xSize*ySize must be less than 2^30, approx 1gigapixel per tile.
This would require more than 2GB of memory to allocate the 'sample count' table. This is not possible on 32 bit architectures, and causes excessive memory allocation on 64 bit architectures.
It is assumed that 'real' files will have much smaller deep tiles (1024x1024 pixels is already quite large), so files that contain tileDescription attributes indicating very large tiles are either corrupt or malicious.
This change is to Deep tiles only. A similar limit is already imposed on regular Tiled images, since the format cannot store compressed tiles with more than 2^31 bytes.
Address:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31390
(additionally, a bug in Imf::CheckFile meant that the large tiles were not being detected)
Signed-off-by: Peter Hillman peterh@wetafx.co.nz