LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1613: Junos OS: BGP session termination upon receipt of specific BGP FlowSpec advertisement.

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.

HighCVSS 8.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is an availability risk for organizations using Juniper Junos OS with BGP FlowSpec. A specially formed FlowSpec advertisement from a BGP peer can cause an established BGP session to terminate, potentially disrupting routing. The issue affects both IPv4 and IPv6 FlowSpec deployments.

Executive priority

Treat this as a high-priority routing availability issue if Juniper BGP FlowSpec is deployed. The main business risk is network disruption, not data theft. Prioritize internet-edge, service-provider, and security-routing environments where BGP session loss could affect traffic flow.

Technical view

CVE-2020-1613 affects Junos OS BGP FlowSpec handling. Receipt of a specific FlowSpec advertisement can make the device send a BGP NOTIFICATION and terminate the session with the originating peer. A fixed Junos device may still propagate the advertisement to vulnerable downstream devices.

Likely exposure

Exposure is most likely on Juniper Junos OS routers, switches, or SRX deployments running listed vulnerable releases and using IPv4 or IPv6 BGP FlowSpec with peers allowed to send FlowSpec advertisements.

Exploitation context

The sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires the vulnerable device to receive the specific BGP FlowSpec advertisement from a BGP peer, so exposure depends on BGP peering and FlowSpec deployment design.

Researcher notes

Key nuance: a patched device may pass the advertisement onward, so validation must consider routing topology, not only single-device patch state. The provided sources identify fixed release thresholds but do not include exploit code, public exploitation evidence, or a standalone workaround.

Mitigation direction

  • Upgrade affected Junos OS releases to the fixed versions named by Juniper and the CVE record.
  • Prioritize devices participating in IPv4 or IPv6 BGP FlowSpec.
  • Assess downstream vulnerable devices, because fixed devices may still propagate the problematic advertisement.
  • Review Juniper JSA10996 for any current vendor-specific guidance before maintenance.
  • Limit FlowSpec acceptance to trusted, necessary BGP peers where operationally feasible.

Validation and detection

  • Inventory Junos OS versions against the affected release list.
  • Identify devices with IPv4 or IPv6 BGP FlowSpec enabled.
  • Map BGP FlowSpec propagation paths, including downstream devices.
  • Review routing logs for BGP NOTIFICATION messages and unexpected FlowSpec-related session resets.
  • Confirm upgraded devices are at or beyond the fixed release thresholds.
Prepared
Confidence
high
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-710: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-1613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H3.94Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2020-1613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS12.3, 15.1, 15.1F, 16.1, 17.1, 17.2, 17.2X75, 17.3, 17.4, 18.1, 18.2X75Listed
Juniper NetworksJunos OS12.3X48, 15.1X49Listed
Juniper NetworksJunos OS14.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Weakness

CWE details

CWE-710

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-710 · source CWE mapping

Improper Adherence to Coding Standards

Improper Adherence to Coding Standards represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs