bgpd: bounds-check when parsing incoming label in nlri #20062
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
Contributor
Author
|
CI:rerun |
Only look at octets we think are valid when parsing a label stack in an NLRI Signed-off-by: Mark Stapp <[email protected]>
mjstapp
force-pushed
the
fix_bgp_label_nlri
branch
from
5572921 to
1b0f890
Compare
Contributor
Author
|
rebased to newer master to clear "rebase" flag |
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.
Only look at octets we think are valid when parsing a label stack in an NLRI
This might lead to a conflict with #19961 so maybe we should wait a bit