ext/phar: Fix ZIP extra field length underflow in Phar#22330
Open
LamentXU123 wants to merge 1 commit into
Open
ext/phar: Fix ZIP extra field length underflow in Phar#22330LamentXU123 wants to merge 1 commit into
LamentXU123 wants to merge 1 commit into
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
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.
Now the parser used a
uint16_tremaining-length counter and subtracted the extra field payload size plus header size without first validating that the parsing data past the extra field boundary.So, a malformed zip .phar file can trigger an underflow. See
the
mtimewill become a controlled 114514191. The malformed ZIP has central extra_len = 4, but the first extra sub-header declares size = 1. The old parser subtracts 5 from a uint16_t length counter, underflows, then continues parsing past the extra field boundary. So it parses file comment bytes as a UT extra field, which makes the mtime 114514191.The fix is to validate each extra field sub-header before consuming it.
p.s. the gpg sign is now fixed.