CVE-2019-0019

BGP packets can trigger rpd crash when BGP tracing is enabled.

HIGH
7.5
CVSS Score
Published: April 10, 2019 at 08:13 PM UTC
Updated: June 17, 2026 at 02:07 AM UTC
1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

16.1 ≤ v < 16.1R7-S4, 16.1R7-S516.2 ≤ v < 16.2R2-S9, 16.2R317.1 ≤ v < 17.1R317.2 ≤ v < 17.2R3-S117.3 ≤ v < 17.3R3-S3, 17.3R3-S4, 17.3R417.4 ≤ v < 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R318.1 ≤ v < 18.1R2-S4, 18.1R3-S4, 18.1R418.2 ≤ v < 18.2R2-S2, 18.2R2-S3, 18.2R318.2X75 ≤ v < 18.2X75-D4018.3 ≤ v < 18.3R1-S3, 18.3R218.4 ≤ v < 18.4R1-S2, 18.4R216.116.1 r116.1 r216.1 r316.1 r416.1 r516.1 r616.216.2 r116.2 r217.117.1 r117.1 r217.217.2 r117.2 r217.2 r317.317.3 r117.3 r217.3 r2-s117.3 r2-s217.3 r317.417.4 r117.4 r1-s117.4 r1-s218.118.1 r118.1 r218.218.2X7518.2x7518.2x75 d2018.2x75 d518.318.3 r118.3 r1-s118.3 r1-s218.418.4 r1
Vendor states this is fixed in 16.1 (unaffected)
Affected range stops below 16.1R7-S4, 16.1R7-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.2R2-S9, 16.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.1R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.2R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.3R3-S3, 17.3R3-S4, 17.3R4, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.1R2-S4, 18.1R3-S4, 18.1R4, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.2R2-S2, 18.2R2-S3, 18.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.2X75-D40, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.3R1-S3, 18.3R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4R1-S2, 18.4R2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

VDB Entryx_refsource_BIDBroken Link
http://www.securityfocus.com/bid/107893
x_refsource_CONFIRMMitigationVendor Advisory
https://kb.juniper.net/JSA10931

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-404NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card