title: Junos OS: Kernel crash (vmcore) during broadcast storm after enabling 'monitor traffic interface fxp0'
description: 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.
problem types: Denial of Service
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7, status: affected, version: 15.1, versionType: custom
lessThan: 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7, status: affected, version: 16.1, versionType: custom
lessThan: 16.2R1-S6, 16.2R2-S5, 16.2R3, status: affected, version: 16.2, versionType: custom
lessThan: 17.1R1-S7, 17.1R2-S7, 17.1R3, status: affected, version: 17.1, versionType: custom
lessThan: 17.2R1-S6, 17.2R2-S4, 17.2R3, status: affected, version: 17.2, versionType: custom
lessThan: 17.2X75-D90, 17.2X75-D110, status: affected, version: 17.2X75, versionType: custom
lessThan: 17.3R1-S4, 17.3R2, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R1-S3, 17.4R2, status: affected, version: 17.4, versionType: custom
}
{
platforms: SRX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X49-D140, status: affected, version: 15.1X49, versionType: custom
}
{
platforms: EX2300, EX3400
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X53-D59, status: affected, version: 15.1X53, versionType: custom
}
{
platforms: QFX10000 Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X53-D67, status: affected, version: 15.1X53, versionType: custom
}
{
platforms: QFX5110, QFX5200
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X53-D233, status: affected, version: 15.1X53, versionType: custom
}
{
platforms: NFX150, NFX250
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X53-D471, 15.1X53-D490, status: affected, version: 15.1X53, versionType: custom
}
metrics:
cvssV3_0: [
attackComplexity: LOW
attackVector: ADJACENT_NETWORK
availabilityImpact: HIGH
baseScore: 5.7
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: REQUIRED
vectorString: CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
version: 3.0
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue: 15.1F6-S11*, 15.1R4-S9, 15.1R6-S6, 15.1R7, 15.1X49-D140, 15.1X53-D233, 15.1X53-D471, 15.1X53-D490, 15.1X53-D59, 15.1X53-D67, 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7, 16.2R1-S6, 16.2R2-S5, 16.2R3, 17.1R1-S7, 17.1R2-S7, 17.1R3, 17.2R1-S6, 17.2R2-S4, 17.2R3, 17.2X75-D110, 17.2X75-D90, 17.3R1-S4, 17.3R2, 17.4R1-S3, 17.4R2, 18.1R1, 18.1X75-D10, and all subsequent releases.
*Future availability
workarounds: Avoid executing the 'monitor traffic interface fxp0' command while attempting to troubleshoot broadcast storms.