Product Affected

This issue can affect any router configured as a PE router in a Point-to-Multipoint/VPLS or L3VPN environment, when the l3vpn-composite-nexthop and indirect-next-hop routing-options are enabled.
Critical
7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C)

Problem


ICMP ping with the record-route or timestamp options can cause an ingress L3VPN PE router to crash in the following two scenarios:
  • an L3VPN PE router is configured with Point-to-Multipoint LSPs that are used as next hops in configuration of static routes to customers' networks
  • an L3VPN PE configured with 'l3vpn-composite-nexthop' and 'indirect-next-hop' under [routing-options] configuration hierarchy.
In both cases, receipt of either ping option will cause the router to crash.

Solution


The situation where the ping options are received by an affected network topology are now handled without triggering an exception.

All JUNOS software releases built on or after 2011-01-21 have fixed this specific issue. Releases containing the fix specifically include: 9.3S18, 10.0S12, 10.2R1, and all subsequent releases (i.e. all releases built after 10.2R1).

This issue is being tracked as PR 493426. While this PR may not viewable by customers, it can be used as a reference when discussing the issue with JTAC.

KB16765 [juniper.net] - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.


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.

Workaround


Disable all ping options that can be used to trigger the issue: 
system {
  no-ping-record-route;
  no-ping-time-stamp;
}
Alternately, create a firewall filter to block all types of possible ping options: 
family inet {
    filter protect {
        term 1 {
            from {
                  ip-options [ route-record timestamp ];
            }
            then {
                  count bad-timestamps;
                  reject;
            }
           }
        term 2 {
                then accept;
        }
    }
}

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Related Information