BGP UPDATE Message Flaws That Could Drop The Session
We've been notified about possible problems with one or possibly more BGP implementations.
1. BGP UPDATE messages with path attributes that contain a code zero (0) can cause an implementation to drop a peering session (and associated routes). BGP recovers, but another message causes the condition again. Depending on the implementation, attributes with code zero should be treated as "unknown" and not "invalid".
2. BGP UPDATE messages with ASSequence path segment of zero (0) length can cause an implementation to incorrectly locate the beginning of the next path segment. This usually results in finding an invalid segment type, and drops the session.
For more information on this vulnerability, visit the following Web site:
Foundry Systems Test Results
BigIron RX with Release 2.5 and NetIron XMR and NetIron MLX with release 3.7 were tested for the above vulnerabilities and we have confirmed that the above Foundry systems products are not affected by these vulnerabilities.