Reject overflowing numeric OID components - #10911
Open
subotac wants to merge 1 commit into
Open
Conversation
Signed-off-by: subotac <73706465+subotac@users.noreply.github.com>
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.
Description
oid_parse_number()checked the accumulated value before multiplying by 10,but did not account for the pending digit. Numeric components such as
4294967296could therefore wrap and be accepted as a different OID value.Validate the complete multiply-add before updating the accumulator, and add
regression cases for overflow to zero, overflow to a nonzero value, and
continued parsing after a wrap.
Fixes #10910
PR checklist