Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2019-0019

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

High7.5EPSS 1.1%
Published
Updated
Reserved
Assigned by
juniper

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.

Scores

CVSS scores of CVE-2019-0019, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.0High7.5CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
1.1% · top 33% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Weakness

Affected products

  • Juniper Networks · Junos OS

    • affected 16.1 – < 16.1R7-S4, 16.1R7-S5
    • affected 16.2 – < 16.2R2-S9, 16.2R3
    • affected 17.1 – < 17.1R3
    • affected 17.2 – < 17.2R3-S1
    • affected 17.3 – < 17.3R3-S3, 17.3R3-S4, 17.3R4
    • affected 17.4 – < 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3
    • affected 18.1 – < 18.1R2-S4, 18.1R3-S4, 18.1R4
    • affected 18.2 – < 18.2R2-S2, 18.2R2-S3, 18.2R3
    • affected 18.2X75 – < 18.2X75-D40
    • affected 18.3 – < 18.3R1-S3, 18.3R2
    • affected 18.4 – < 18.4R1-S2, 18.4R2
    • unaffected all – < 16.1

What to do

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.

Workaround: The issue can be mitigated by disabling BGP tracing. Use authentication for BGP (tcp-md5, ipsec, etc.) to mitigate the issue.

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-0019 badge
[![CVE-2019-0019](https://trackcve.app/badge/CVE-2019-0019.svg)](https://trackcve.app/cve/CVE-2019-0019)

Record last updated .