BGP packets can trigger rpd crash when BGP tracing is enabled.
Published Apr 10, 2019
7.5
HIGHCVSS 3.1
EPSS 1.14%
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.
Affected products
-
- Version 16.1StatusaffectedConstraints<16.1R7-S4, 16.1R7-S5
- Version 16.2StatusaffectedConstraints<16.2R2-S9, 16.2R3
- Version 17.1StatusaffectedConstraints<17.1R3
- Version 17.2StatusaffectedConstraints<17.2R3-S1
- Version 17.3StatusaffectedConstraints<17.3R3-S3, 17.3R3-S4, 17.3R4
- Version 17.4StatusaffectedConstraints<17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3
- Version 18.1StatusaffectedConstraints<18.1R2-S4, 18.1R3-S4, 18.1R4
- Version 18.2StatusaffectedConstraints<18.2R2-S2, 18.2R2-S3, 18.2R3
- Version 18.2X75StatusaffectedConstraints<18.2X75-D40
- Version 18.3StatusaffectedConstraints<18.3R1-S3, 18.3R2
- Version 18.4StatusaffectedConstraints<18.4R1-S2, 18.4R2
- Version allStatusunaffectedConstraints<16.1
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Juniper Networks | Junos OS | n/a |
|
Configuration 1
Configuration 4
Configuration 5
Configuration 6
Configuration 9
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
Vendor solution
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.
References (2)
- http://www.securityfocus.com/bid/107893 vdb-entryx_refsource_BIDBroken Link
- https://kb.juniper.net/JSA10931 x_refsource_CONFIRMMitigationVendor Advisory
| Link | Providers | Tags |
|---|---|---|
| http://www.securityfocus.com/bid/107893 | vdb-entryx_refsource_BIDBroken Link | |
| https://kb.juniper.net/JSA10931 | x_refsource_CONFIRMMitigationVendor Advisory |
Change history (0)
No recorded changes yet.