A crafted RSVP Path Object overloads the routing protocol daemon (RPD) process when received by a JUNOS Router. The crafted packet triggers a flaw which consumes close to 100% of the RE CPU time. The RPD process becomes unresponsive to commands via the management console, and all routing protocol updates are not processed (resulting on in all the routing protocols to drop their sessions). The RPD process does not recover on its own, requiring manual intervention. This issue was discovered through systems and certification testing in a customer lab.
All JUNOS software releases built on or after March 27, 2009 have been corrected to properly handle these crafted RSVP Path Object. This specifically includes 8.1S1, 8.5S1, 9.0S2, 9.1S2, 9.2R2, 9.3R1, 9.4R1, and all subsequent releases. PR Reference for this issue is 296141. (Note: the RSVP Security issue PSN-2010-01-625 is fixed with the same PR. These are two different conditions but where fixed with the same PR.) RSVP Authentication is an effective mitigation technique to limit the exposure to this RSVP issue. The JUNOS documentation has configuration examples to properly configure RSVP Authentication. For example, the example for JUNOS 10.0 is here: http://www.juniper.net/techpubs/en_US/junos10.0/information-products/topic-collections/config-guide-mpls-applications/frameset.html. Filtering RSVP packets on the edge of the network with iACL (Infrastructure ACLs) is another mitigation technique which will limit the exposure of this issue.
How to obtain Service Releases: Security vulnerabilities are fixed in the next available Maintenance Release of each supported JUNOS version. In some cases, a Maintenance Release is not planned to be available in an appropriate time-frame. For these cases, Service Releases are made available in order to be more timely. Security Advisory notices will indicate which Maintenance and/or Service Releases contain fixes for the issues described. Upon request to JTAC, customers will be provided download instructions for a Service Release. Although Juniper does not provide formal Release Note documentation for a Service Release, a list of "PRs fixed" can be provided on request.