While experiencing a broadcast storm, placing the fxp0 interface into promiscuous mode via the monitor traffic interface fxp0 can cause the system to crash and restart (vmcore). This issue only affects Junos OS 15.1 and later releases, and affects both single core and multi-core REs. Releases prior to Junos OS 15.1 are unaffected by this vulnerability. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7; 15.1X49 versions prior to 15.1X49-D140; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400; 15.1X53 versions prior to 15.1X53-D67 on QFX10K; 15.1X53 versions prior to 15.1X53-D233 on QFX5200/QFX5110; 15.1X53 versions prior to 15.1X53-D471, 15.1X53-D490 on NFX; 16.1 versions prior to 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7; 16.2 versions prior to 16.2R1-S6, 16.2R2-S5, 16.2R3; 17.1 versions prior to 17.1R1-S7, 17.1R2-S7, 17.1R3; 17.2 versions prior to 17.2R1-S6, 17.2R2-S4, 17.2R3; 17.2X75 versions prior to 17.2X75-D90, 17.2X75-D110; 17.3 versions prior to 17.3R1-S4, 17.3R2; 17.4 versions prior to 17.4R1-S3, 17.4R2.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Junos | Juniper | 15.1 (including) | 15.1 (including) |
| Junos | Juniper | 15.1-a1 (including) | 15.1-a1 (including) |
| Junos | Juniper | 15.1-f1 (including) | 15.1-f1 (including) |
| Junos | Juniper | 15.1-f2 (including) | 15.1-f2 (including) |
| Junos | Juniper | 15.1-f2-s1 (including) | 15.1-f2-s1 (including) |
| Junos | Juniper | 15.1-f2-s2 (including) | 15.1-f2-s2 (including) |
| Junos | Juniper | 15.1-f2-s3 (including) | 15.1-f2-s3 (including) |
| Junos | Juniper | 15.1-f2-s4 (including) | 15.1-f2-s4 (including) |
| Junos | Juniper | 15.1-f3 (including) | 15.1-f3 (including) |
| Junos | Juniper | 15.1-f4 (including) | 15.1-f4 (including) |
| Junos | Juniper | 15.1-f5 (including) | 15.1-f5 (including) |
| Junos | Juniper | 15.1-f6 (including) | 15.1-f6 (including) |
| Junos | Juniper | 15.1-r4-s9 (including) | 15.1-r4-s9 (including) |
| Junos | Juniper | 15.1-r6-s6 (including) | 15.1-r6-s6 (including) |
| Junos | Juniper | 15.1-r7 (including) | 15.1-r7 (including) |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.