CVE-2019-0028

Junos OS: RPD process crashes due to specific BGP peer restarts condition.

Description

On Junos devices with the BGP graceful restart helper mode enabled or the BGP graceful restart mechanism enabled, a BGP session restart on a remote peer that has the graceful restart mechanism enabled may cause the local routing protocol daemon (RPD) process to crash and restart. By simulating a specific BGP session restart, an attacker can repeatedly crash the RPD process causing prolonged denial of service (DoS). Graceful restart helper mode for BGP is enabled by default. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS: 16.1 versions prior to 16.1R7; 16.1X65 versions prior to 16.1X65-D48; 16.2 versions prior to 16.2R2-S8; 17.1 versions prior to 17.1R2-S7, 17.1R3; 17.2 versions prior to 17.2R1-S7, 17.2R3; 17.2X75 versions prior to 17.2X75-D92, 17.2X75-D102, 17.2X75-D110; 17.3 versions prior to 17.3R2-S2, 17.3R3; 17.4 versions prior to 17.4R1-S4, 17.4R2; 18.1 versions prior to 18.1R2. Junos OS releases prior to 16.1R1 are not affected.

Remediation

Solution:

  • The following software releases have been updated to resolve this specific issue: 16.1R7, 16.1X65-D48, 16.2R2-S8, 17.1R2-S7, 17.1R3, 17.2R1-S7, 17.2R3, 17.2X75-D102, 17.2X75-D110, 17.2X75-D92, 17.3R2-S2, 17.3R3, 17.4R1-S4, 17.4R2, 18.1R2, 18.2R1, 18.2X75-D5, and all subsequent releases.

Workaround:

  • This issue can be prevented by disabling the BGP graceful restart mechanism, including graceful restart helper mode: [protocols bgp graceful-restart disable] Furthermore, the risk associated with this issue can be mitigated by limiting BGP sessions only from trusted peers.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.49%
Vendor Advisory juniper.net
Affected: Juniper Networks Junos OS
Published at:
Updated at:

References

Link Tags
https://kb.juniper.net/JSA10932 mitigation vendor advisory
http://www.securityfocus.com/bid/107892 vdb entry broken link

Frequently Asked Questions

What is the severity of CVE-2019-0028?
CVE-2019-0028 has been scored as a high severity vulnerability.
How to fix CVE-2019-0028?
To fix CVE-2019-0028: The following software releases have been updated to resolve this specific issue: 16.1R7, 16.1X65-D48, 16.2R2-S8, 17.1R2-S7, 17.1R3, 17.2R1-S7, 17.2R3, 17.2X75-D102, 17.2X75-D110, 17.2X75-D92, 17.3R2-S2, 17.3R3, 17.4R1-S4, 17.4R2, 18.1R2, 18.2R1, 18.2X75-D5, and all subsequent releases.
Is CVE-2019-0028 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-0028 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-0028?
CVE-2019-0028 affects Juniper Networks Junos OS.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.