fix: bound affinity entry decompression - #28
Merged
Conversation
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
2 participants
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.
fixes #27
reject an entry whose declared size is past a flat 1 GiB ceiling before any branch decompresses, and bound the zstd read to the declared size rather than letting
read_to_endrun unbounded. drops thewith_capacitythat reserved from the untrusted field.the ceiling is deliberately a flat size, not a multiple of the compressed bytes. a ratio cap looks tighter but rejects real files: a blank tile compresses by more than 4000x, which broke the existing container round-trip test when i tried it.
tests cover both directions, the absurd declaration and an ordinary entry that must still decode.
before
after