First published: Wed Oct 10 2018(Updated: )
Receipt of a specially crafted IPv6 exception packet may be able to trigger a kernel crash (vmcore), causing the device to reboot. The issue is specific to the processing of Broadband Edge (BBE) client route processing on MX Series subscriber management platforms, introduced by the Tomcat (Next Generation Subscriber Management) functionality in Junos OS 15.1. This issue affects no other platforms or configurations. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1R7-S2, 15.1R8 on MX Series; 16.1 versions prior to 16.1R4-S11, 16.1R7-S2, 16.1R8 on MX Series; 16.2 versions prior to 16.2R3 on MX Series; 17.1 versions prior to 17.1R2-S9, 17.1R3 on MX Series; 17.2 versions prior to 17.2R2-S6, 17.2R3 on MX Series; 17.3 versions prior to 17.3R2-S4, 17.3R3-S2, 17.3R4 on MX Series; 17.4 versions prior to 17.4R2 on MX Series; 18.1 versions prior to 18.1R2-S3, 18.1R3 on MX Series; 18.2 versions prior to 18.2R1-S1, 18.2R2 on MX Series.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | =15.1 | |
Juniper JUNOS | =15.1-f2 | |
Juniper JUNOS | =15.1-f3 | |
Juniper JUNOS | =15.1-f4 | |
Juniper JUNOS | =15.1-f5 | |
Juniper JUNOS | =15.1-f6 | |
Juniper JUNOS | =15.1-f7 | |
Juniper JUNOS | =15.1-r1 | |
Juniper JUNOS | =15.1-r2 | |
Juniper JUNOS | =15.1-r3 | |
Juniper JUNOS | =15.1-r4 | |
Juniper JUNOS | =15.1-r5 | |
Juniper JUNOS | =15.1-r6 | |
Juniper JUNOS | =16.1 | |
Juniper JUNOS | =16.1-r1 | |
Juniper JUNOS | =16.1-r2 | |
Juniper JUNOS | =16.1-r3 | |
Juniper JUNOS | =16.1-r5 | |
Juniper JUNOS | =16.1-r6 | |
Juniper JUNOS | =16.2 | |
Juniper JUNOS | =16.2-r1 | |
Juniper JUNOS | =16.2-r2 | |
Juniper JUNOS | =17.1 | |
Juniper JUNOS | =17.1-r1 | |
Juniper JUNOS | =17.2 | |
Juniper JUNOS | =17.2-r1 | |
Juniper JUNOS | =17.3 | |
Juniper JUNOS | =17.3-r1 | |
Juniper JUNOS | =17.4 | |
Juniper JUNOS | =17.4-r1 | |
Juniper JUNOS | =18.1 | |
Juniper JUNOS | =18.1-r1 | |
Juniper JUNOS | =18.2 |
The following software releases have been updated to resolve this specific issue: 15.1R7-S2, 15.1R8, 16.1R4-S11, 16.1R7-S2, 16.1R8, 16.2R3, 17.1R2-S9, 17.1R3, 17.2R2-S6, 17.2R3, 17.3R2-S4, 17.3R3-S2*, 17.3R4, 17.4R2, 18.1R2-S3, 18.1R3, 18.2R1-S1, 18.2R2, 18.3R1, and all subsequent releases. *Available November 2018
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.