title: Junos OS: MX Series: uncontrolled recursion and crash in Broadband Edge subscriber management daemon (bbe-smgd).
description: Receipt of a malformed packet on MX Series devices with dynamic vlan configuration can trigger an uncontrolled recursion loop in the Broadband Edge subscriber management daemon (bbe-smgd), and lead to high CPU usage and a crash of the bbe-smgd service. Repeated receipt of the same packet can result in an extended denial of service condition for the device. Affected releases are Juniper Networks Junos OS: 16.1 versions prior to 16.1R7-S1; 16.2 versions prior to 16.2R2-S7; 17.1 versions prior to 17.1R2-S10, 17.1R3; 17.2 versions prior to 17.2R3; 17.3 versions prior to 17.3R3-S1; 17.4 versions prior to 17.4R2; 18.1 versions prior to 18.1R3; 18.2 versions prior to 18.2R2.
problem types: CWE-674: Uncontrolled Recursion
affected:
{
platforms: MX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 16.1R7-S1, status: affected, version: 16.1, versionType: custom
lessThan: 16.2R2-S7, status: affected, version: 16.2, versionType: custom
lessThan: 17.1R2-S10, 17.1R3, status: affected, version: 17.1, versionType: custom
lessThan: 17.2R3, status: affected, version: 17.2, versionType: custom
lessThan: 17.3R3-S1, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R2, status: affected, version: 18.2, versionType: custom
}
metrics:
cvssV3_0: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Junos OS releases have been updated to resolve this specific issue: 16.1R7-S1, 16.2R2-S7, 17.1R2-S10, 17.1R3, 17.2R3, 17.3R3-S1, 17.4R2, 18.1R3, 18.2R2, 18.3R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.