No exploitation reported

CVE-2019-0019

No exploitation reported by the sources we read.

Published2019-04-10
WeaknessCWE-404

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC

2019-04-1020:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-0019?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-0019?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Juniper junos

Branch	Affected	Fixed in	Source
16.1	= 16.1	no fix published	NVD
16.2	= 16.2	no fix published	NVD
17.1	= 17.1	no fix published	NVD
17.2	= 17.2	no fix published	NVD
17.3	= 17.3	no fix published	NVD
17.4	= 17.4	no fix published	NVD
18.1	= 18.1	no fix published	NVD
18.2	= 18.2x75	no fix published	NVD
18.3	= 18.3	no fix published	NVD
18.4	= 18.4	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

kb.juniper.netMitigation · Vendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.17.5read 2026-10-23
CNACVSS 3.07.5read 2026-10-23
NVDCVSS 2.05read 2026-10-23
CNAweakness (CWE)CWE-404read 2026-10-23
FIRST EPSSEPSS score1.1 %2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2019-04-10
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2019-0019?

Is CVE-2019-0019 actively exploited?

Active exploitation of CVE-2019-0019 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-0019?

CVE-2019-0019 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database