Repository navigation
Enforce limits before intermediate raster allocations - #20
Merged
smnandre merged 2 commits intoSep 27, 2026
Merged
Conversation
smnandre
force-pushed
the
security/intermediate-raster-limits
branch
from
September 27, 2026 13:21
c5f6d1e to
9639538
Compare
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
1 participant
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.
A large resize, extension, or rotation followed by a small crop could pass final-output checks while allocating an oversized intermediate raster.
Apply strict output limits before each built-in operation in both drivers, using the actual current dimensions so the same protection works after dynamic trimming. Explicit non-strict policies and trusted escape callbacks retain their documented behavior.