-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bgpd: Flowspec overflow issue #12884
Conversation
According to the flowspec RFC 8955 a flowspec nlri is <length, <nlri data>> Specifying 0 as a length makes BGP get all warm on the inside. Which in this case is not a good thing at all. Prevent warmth, stay cold on the inside. Reported-by: Iggy Frankovic <iggyfran@amazon.com> Signed-off-by: Donald Sharp <sharpd@nvidia.com>
|
@Mergifyio backport dev/8.5 stable/8.4 stable/8.3 stable/8.2 stable/8.1 |
✅ Backports have been created
|
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-9871/ This is a comment from an automated CI system. |
bgpd: Flowspec overflow issue (backport #12884)
bgpd: Flowspec overflow issue (backport #12884)
bgpd: Flowspec overflow issue (backport #12884)
bgpd: Flowspec overflow issue (backport #12884)
bgpd: Flowspec overflow issue (backport #12884)
According to the flowspec RFC 8955 a flowspec nlri is <length, > Specifying 0 as a length makes BGP get all warm on the inside. Which in this case is not a good thing at all. Prevent warmth, stay cold on the inside.
Reported-by: Iggy Frankovic iggyfran@amazon.com