Prevent overflow in file-lines range normalization - #6993
Open
cuishuang wants to merge 1 commit into
Open
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.
Fixes #6992
Range::adjacent_topreviously added one directly to user-controlled--file-linesupper bounds. An upper bound ofusize::MAXcould therefore panic when overflow checks were enabled or wrap in release builds.The wrapping case could also incorrectly merge non-adjacent ranges because the JSON parser accepted line zero, despite
--file-linesbeing documented as 1-based.This change:
checked_addfor range adjacency checks;--file-lines;usize::MAXas a valid upper bound;