dbcve.org
JunosOperating system · Juniper

CVE-2020-1613

HIGH · 7.5 CVSS v3.1 Published 2020-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the BGP FlowSpec implementation may cause a Juniper Networks Junos OS device to terminate an established BGP session upon receiving a specific BGP FlowSpec advertisement. The BGP NOTIFICATION message that terminates an established BGP session is sent toward the peer device that originally sent the specific BGP FlowSpec advertisement. This specific BGP FlowSpec advertisement received from a BGP peer might get propagated from a Junos OS device running the fixed release to another device that is vulnerable causing BGP session termination downstream. This issue affects IPv4 and IPv6 BGP FlowSpec deployment. This issue affects Juniper Networks Junos OS: 12.3; 12.3X48 on SRX Series; 14.1X53 on EX and QFX Series; 15.1 versions prior to 15.1R7-S5; 15.1F versions prior to 15.1F6-S13; 15.1X49 versions prior to 15.1X49-D180 on SRX Series; 15.1X53 versions prior to 15.1X53-D238 on QFX5200/QFX5110; 15.1X53 versions prior to 15.1X53-D497 on NFX Series; 15.1X53 versions prior to 15.1X53-D592 on EX2300/EX3400; 16.1 versions prior to 16.1R7-S7; 17.1 versions prior to 17.1R2-S12, 17.1R3; 17.2 versions prior to 17.2R2-S7, 17.2R3; 17.2X75 versions prior to 17.2X75-D102, 17.2X75-D110, 17.2X75-D44; 17.3 versions prior to 17.3R2-S5, 17.3R3-S5; 17.4 versions prior to 17.4R1-S8, 17.4R2; 18.1 versions prior to 18.1R2-S4, 18.1R3; 18.2X75 versions prior to 18.2X75-D20.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the BGP FlowSpec implementation in Juniper Junos OS allows a specially crafted BGP FlowSpec advertisement to trigger the device to send a BGP NOTIFICATION message that terminates the established BGP session with the peer that sent the malicious advertisement. This causes denial of service by disrupting BGP peering sessions. The malicious advertisement can propagate from a fixed device to vulnerable downstream devices, affecting both IPv4 and IPv6 BGP FlowSpec deployments.

MitigationUpgrade Junos OS to a fixed release (15.1R7-S5, 15.1F6-S13, 16.1R7-S7, 17.1R2-S12, 17.2R2-S7, 17.3R2-S5, 17.4R1-S8, 18.1R2-S4, or later as specified in the advisory). If upgrading is not immediately feasible, consider disabling BGP FlowSpec or implementing BGP prefix filtering to block untrusted FlowSpec advertisements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 12.3= 15.1= 16.1= 17.1= 17.2= 17.2x75= 17.3= 17.4= 18.1= 18.2x75= 18.2x75-d10= 12.3x48

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Junos OS version
    Run 'show version' or 'show system information' to obtain the installed Junos OS version
    Affected if The installed version matches any of the following version families: 12.3, 12.3X48, 15.1, 15.1F6, 16.1, 17.1, 17.2, 17.2X75, 17.3, 17.4, 18.1, 18.2X75, or 18.2X75-D10 (these are the affected versions per the advisory)
  2. Verify BGP FlowSpec is configured
    Run 'show configuration protocols bgp' and look for 'flow-specification' or 'family inet flow' or 'family inet6 flow' under the BGP configuration
    Affected if BGP FlowSpec (flow-specification) is enabled under the BGP protocol configuration
  3. Check for active BGP FlowSpec neighbors
    Run 'show bgp neighbor' or 'show bgp summary' and look for neighbors with FlowSpec family (inet flow or inet6 flow)
    Affected if There are active BGP peers exchanging FlowSpec routes
  4. Review logs for BGP NOTIFICATION messages
    Check system logs (syslog) or run 'show log messages' and search for 'NOTIFICATION' related to BGP, especially after receiving FlowSpec advertisements
    Affected if BGP NOTIFICATION messages appear in logs indicating session termination with FlowSpec peers

The environment is affected if the Junos OS version falls within the affected version range AND BGP FlowSpec is enabled and actively used with BGP peers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to a fixed release (15.1R7-S5, 15.1F6-S13, 16.1R7-S7, 17.1R2-S12, 17.2R2-S7, 17.3R2-S5, 17.4R1-S8, 18.1R2-S4, or later as specified in the advisory). If upgrading is not immediately feasible, consider disabling BGP FlowSpec or implementing BGP prefix filtering to block untrusted FlowSpec advertisements.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data