CVE-2020-1646

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 40% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

On Juniper Networks Junos OS and Junos OS Evolved devices, processing a specific UPDATE for an EBGP peer can lead to a routing process daemon (RPD) crash and restart. This issue occurs only when the device is receiving and processing the BGP UPDATE for an EBGP peer. This issue does not occur when the device is receiving and processing the BGP UPDATE for an IBGP peer. However, the offending BGP UPDATE can originally come from an EBGP peer, propagates through the network via IBGP peers without causing crash, then it causes RPD crash when it is processed for a BGP UPDATE towards an EBGP peer. Repeated receipt and processing of the same specific BGP UPDATE can result in an extended Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS: 17.3R3-S6, 17.4R2-S7, and 18.1R3-S7. Juniper Networks Junos OS Evolved 19.2R2-EVO and later versions, prior to 19.3R1-EVO. Other Junos OS releases are not affected.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
59.3%
KEV
Not listed

Published

July 17, 2020

Last Modified

November 21, 2024

References (2)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 16:59 UTCEPSS rescore
  2. 2026-07-15 16:55 UTCEPSS rescore
  3. 2026-07-15 01:57 UTCEPSS rescore
  4. 2026-07-13 22:27 UTCEPSS rescore
  5. 2026-07-13 22:27 UTCEPSS rescore
  6. 2026-07-13 06:10 UTCEPSS rescore
  7. 2026-07-13 06:10 UTCEPSS rescore
  8. 2026-07-12 05:44 UTCEPSS rescore
  9. 2026-07-11 08:25 UTCEPSS rescore
  10. 2026-07-11 08:25 UTCEPSS rescore
  11. 2026-07-09 19:07 UTCEPSS rescore
  12. 2026-07-08 15:12 UTCEPSS rescore
  13. 2026-07-07 13:43 UTCEPSS rescore
  14. 2026-07-07 13:43 UTCEPSS rescore
  15. 2026-07-06 16:25 UTCEPSS rescore
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-06 02:21 UTCEPSS rescore
  18. 2026-07-06 02:21 UTCEPSS rescore
  19. 2026-07-05 02:27 UTCEPSS rescore
  20. 2026-07-04 06:29 UTCEPSS rescore
  21. 2026-07-04 06:28 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-30 23:20 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-28 14:05 UTCEPSS rescore
Show 59 more
  1. 2026-06-28 04:54 UTCEPSS rescore
  2. 2026-06-28 04:54 UTCEPSS rescore
  3. 2026-06-27 03:06 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-24 14:03 UTCEPSS rescore
  6. 2026-06-24 14:03 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-22 14:23 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-21 14:54 UTCEPSS rescore
  12. 2026-06-21 14:54 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-19 19:23 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:46 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-13 22:58 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:10 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
  26. 2026-06-10 22:16 UTCEPSS rescore
  27. 2026-06-10 22:16 UTCEPSS rescore
  28. 2026-06-10 13:20 UTCEPSS rescore
  29. 2026-06-08 14:15 UTCEPSS rescore
  30. 2026-06-08 14:15 UTCEPSS rescore
  31. 2026-06-07 15:23 UTCEPSS rescore
  32. 2026-06-07 15:23 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-05 22:45 UTCEPSS rescore
  36. 2026-06-05 22:45 UTCEPSS rescore
  37. 2026-06-05 06:08 UTCEPSS rescore
  38. 2026-06-05 06:08 UTCEPSS rescore
  39. 2026-06-04 13:10 UTCEPSS rescore
  40. 2026-06-04 13:10 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-02 20:11 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-06-01 13:50 UTCEPSS rescore
  45. 2026-05-31 22:29 UTCEPSS rescore
  46. 2026-05-31 22:29 UTCEPSS rescore
  47. 2026-05-31 00:15 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-29 13:42 UTCEPSS rescore
  50. 2026-05-28 13:43 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-27 13:39 UTCEPSS rescore
  53. 2026-05-27 01:00 UTCEG score recompute
  54. 2026-05-27 01:00 UTCGHSA enrichment
  55. 2026-05-26 13:42 UTCEPSS rescore
  56. 2026-05-26 13:42 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-24 16:48 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-1646?
CVE-2020-1646 is a high vulnerability published on July 17, 2020. On Juniper Networks Junos OS and Junos OS Evolved devices, processing a specific UPDATE for an EBGP peer can lead to a routing process daemon (RPD) crash and restart. This issue occurs only when the device is receiving and processing the BGP UPDATE for an EBGP peer. This issue does not occur when…
When was CVE-2020-1646 disclosed?
CVE-2020-1646 was first published in the National Vulnerability Database on July 17, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-1646 actively exploited?
CVE-2020-1646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-1646?
CVE-2020-1646 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2020-1646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-1646, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-1646

Explore →

Is Your Infrastructure Affected by CVE-2020-1646?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs