Actually check the framesize in FliDecode.c #5659
Merged
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.
FliDecode.c had a check in the head of the frame where it was checking a variable against the value that was just set.
This updates the check to check the bytes in the buffer vs the framesize.
Note that there are potentially single bytes of padding, such that all the sizes should be even. This isn't necessarily reflected in the file size (e.g.
hopper.fli
) especially on the last chunk.