MX Series: In BBE configurations, receipt of a crafted IPv6 exception packet causes a Denial of Service
Juniper Networks Junos OS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS MX Series |
| No fix yet |
Juniper Networks Junos OS
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS MX Series |
| No fix yet |
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.
From the CVE record · juniper
On MX Series subscriber management platforms using Tomcat functionality, Junos OS may crash and reboot when it receives a specially crafted IPv6 exception packet. The issue is specific to BBE client route processing; the input does not specify whether authentication or user interaction is required.
Operators of MX Series subscriber management platforms running Tomcat functionality should check Junos OS 15.1, 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, 18.1, or 18.2 releases against the affected-version thresholds.