LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0259: Junos OS and Junos OS Evolved: QFX5K Series: Underlay network traffic might not be processed upon receipt of high rate of specific genuine overlay packets in VXLAN scenario

Due to a vulnerability in DDoS protection in Juniper Networks Junos OS and Junos OS Evolved on QFX5K Series switches in a VXLAN configuration, instability might be experienced in the underlay network as a consequence of exceeding the default ddos-protection aggregate threshold. If an attacker on a client device on the overlay network sends a high volume of specific, legitimate traffic in the overlay network, due to an improperly detected DDoS violation, the leaf might not process certain L2 traffic, sent by spines in the underlay network. Continued receipt and processing of the high volume traffic will sustain the Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS on QFX5K Series: 17.3 versions prior to 17.3R3-S11; 17.4 versions prior to 17.4R3-S5; 18.1 versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R2-S8, 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R1-S8, 18.4R2-S6, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6, 19.2R3-S2; 19.3 versions prior to 19.3R3-S2; 19.4 versions prior to 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S2, 20.3R2. Juniper Networks Junos OS Evolved on QFX5220: All versions prior to 20.3R2-EVO.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can make Juniper QFX5K leaf switches in VXLAN environments stop processing some underlay L2 traffic when high-rate legitimate overlay traffic triggers DDoS protection incorrectly. The business impact is availability loss in data-center fabrics, not data theft or modification.

Executive priority

Treat this as a high-priority availability risk for Juniper VXLAN data-center fabrics. It is most urgent where QFX5K leaf switches support critical services or multi-tenant overlay clients.

Technical view

CVE-2021-0259 affects Junos OS and Junos OS Evolved on QFX5K Series switches in VXLAN configurations. A client on the overlay can send high volumes of specific genuine packets, causing an improperly detected DDoS violation and sustained DoS affecting underlay traffic from spines.

Likely exposure

Exposure is limited to Juniper QFX5K Series VXLAN deployments running affected Junos OS releases, plus QFX5220 on Junos OS Evolved before 20.3R2-EVO. Non-VXLAN deployments or other platforms are not identified in the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The described attacker position is an unauthenticated client device on the overlay network able to generate high-volume legitimate traffic.

Researcher notes

The key condition is an improperly detected DDoS violation after high-rate legitimate overlay traffic exceeds the default aggregate threshold. The public description does not provide packet specifics, public exploit details, or a workaround beyond fixed release guidance.

Mitigation direction

  • Upgrade affected Junos OS versions to the fixed releases listed in JSA11150.
  • Upgrade Junos OS Evolved on QFX5220 to 20.3R2-EVO or later.
  • Prioritize VXLAN leaf switches supporting critical underlay fabric connectivity.
  • If upgrade timing is constrained, check Juniper JSA11150 for supported interim guidance.

Validation and detection

  • Inventory QFX5K and QFX5220 switches used in VXLAN configurations.
  • Compare installed Junos versions with the affected and fixed release ranges.
  • Review telemetry for DDoS-protection threshold events and underlay L2 processing instability.
  • Confirm whether overlay clients can generate sustained high-rate traffic toward affected leaf switches.
Prepared
Confidence
high
Sources
3

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-755: 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-2021-0259 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
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/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
7.4CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H2.84Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2021-0259Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/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 OS17.3, 17.4, 18.1, 18.2, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3Listed
Juniper NetworksJunos OS EvolvedunspecifiedListed
Weakness

CWE details

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

CWE-755 · source CWE mapping

Improper Handling of Exceptional Conditions

Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.