This issue can affect all devices running Junos OS 10.0 or later with PIM configured in a Next-Generation Multicast VPN (NGEN MVPN) environment.
Receipt of a large number of crafted IPv4 or IPv6 PIM join messages in a Next-Generation Multicast VPN (NGEN MVPN) environment can trigger the RPD routing daemon to crash. The flood consists of specially crafted PIM (S,G) joins that, while syntactically valid, are not common in a typical multicast environment. Once a large amount of these PIM joins are received by the router, RPD crashes and restarts.
Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
This issue affects products running Junos OS 10.0 or later, and only applies to PIM in an NGEN MVPN environment. No other Juniper Networks products or platforms are affected by this issue.
All Junos OS software releases built on or after 2012-09-27 have fixed this specific issue. Releases containing the fix specifically include: 10.0S28, 10.4R7, 11.1R5, 11.2R2, 11.4R1, and all subsequent releases (i.e. all releases built after 11.4R1).
Customers can confirm the build date of any Junos OS release by issuing the command 'show version detail'.
This issue is being tracked as PR 669783 and is visible on the Customer Support website.
KB16765 - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.
Use access lists or firewall filters to limit PIM access to the router only from trusted hosts.
How to obtain fixed software:
Security vulnerabilities in Junos 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 and Security Notices will indicate which Maintenance and 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.