title: BGP packets can trigger rpd crash when BGP tracing is enabled.
description: When BGP tracing is enabled an incoming BGP message may cause the Junos OS routing protocol daemon (rpd) process to crash and restart. While rpd restarts after a crash, repeated crashes can result in an extended DoS condition. Affected releases are Juniper Networks Junos OS: 16.1 versions prior to 16.1R7-S4, 16.1R7-S5; 16.2 versions prior to 16.2R2-S9, 16.2R3; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R3-S1; 17.3 versions prior to 17.3R3-S3, 17.3R3-S4, 17.3R4; 17.4 versions prior to 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S4, 18.1R4; 18.2 versions prior to 18.2R2-S2, 18.2R2-S3, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S3, 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2. This issue does not affect Junos releases prior to 16.1R1.
problem types: CWE-404 Improper Resource Shutdown or Release
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 16.1R7-S4, 16.1R7-S5, status: affected, version: 16.1, versionType: custom
lessThan: 16.2R2-S9, 16.2R3, status: affected, version: 16.2, versionType: custom
lessThan: 17.1R3, status: affected, version: 17.1, versionType: custom
lessThan: 17.2R3-S1, status: affected, version: 17.2, versionType: custom
lessThan: 17.3R3-S3, 17.3R3-S4, 17.3R4, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R2-S4, 18.1R3-S4, 18.1R4, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R2-S2, 18.2R2-S3, 18.2R3, status: affected, version: 18.2, versionType: custom
lessThan: 18.2X75-D40, status: affected, version: 18.2X75, versionType: custom
lessThan: 18.3R1-S3, 18.3R2, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R1-S2, 18.4R2, status: affected, version: 18.4, versionType: custom
lessThan: 16.1, status: unaffected, version: all, 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 software releases have been updated to resolve this specific issue: 16.1R7-S4, 16.1R7-S5, 16.2R2-S9, 16.2R3, 17.1R3, 17.2R3-S1, 17.3R3-S3, 17.3R3-S4, 17.3R4, 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3, 18.1R2-S4, 18.1R3-S4, 18.1R4, 18.2R2-S2, 18.2R2-S3, 18.2R3, 18.2X75-D40, 18.3R1-S3, 18.3R2, 18.4R1-S2, 18.4R2, 19.1R1, and all subsequent releases.
workarounds: The issue can be mitigated by disabling BGP tracing.
Use authentication for BGP (tcp-md5, ipsec, etc.) to mitigate the issue.