CVE-2021-0234

Junos OS: QFX5100-96S: DDoS protection does not work as expected.

MEDIUM

5.8

CVSS Score

Published: April 22, 2021 at 07:37 PM UTC

Updated: June 17, 2026 at 03:29 AM UTC

2 products affected across 2 vendorsJunosQfx5100-96S

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.8

Exploit prediction

EPSS 0.9%

Description

Due to an improper Initialization vulnerability on Juniper Networks Junos OS QFX5100-96S devices with QFX 5e Series image installed, ddos-protection configuration changes will not take effect beyond the default DDoS (Distributed Denial of Service) settings when configured from the CLI. The DDoS protection (jddosd) daemon allows the device to continue to function while protecting the packet forwarding engine (PFE) during the DDoS attack. When this issue occurs, the default DDoS settings within the PFE apply, as CPU bound packets will be throttled and dropped in the PFE when the limits are exceeded. To check if the device has this issue, the administrator can execute the following command to monitor the status of DDoS protection: user@device> show ddos-protection protocols error: the ddos-protection subsystem is not running This issue affects only QFX5100-96S devices. No other products or platforms are affected by this issue. This issue affects: Juniper Networks Junos OS on QFX5100-96S: 17.3 versions prior to 17.3R3-S10; 17.4 versions prior to 17.4R3-S4; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R3-S3; 18.3 versions prior to 18.3R3-S2; 18.4 versions prior to 18.4R2-S4, 18.4R3-S1; 19.1 versions prior to 19.1R3, 19.1R3-S4; 19.2 versions prior to 19.2R2; 19.3 versions prior to 19.3R3; 19.4 versions prior to 19.4R2;

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

17.3 ≤ v < 17.3R3-S1017.4 ≤ v < 17.4R3-S418.1 ≤ v < 18.1R3-S1018.2 ≤ v < 18.2R3-S318.3 ≤ v < 18.3R3-S218.4 ≤ v < 18.4R2-S4, 18.4R3-S119.1 ≤ v < 19.1R3, 19.1R3-S419.2 ≤ v < 19.2R219.3 ≤ v < 19.3R319.4 ≤ v < 19.4R217.3 17.3 r1 17.3 r1-s1 17.3 r1-s4 17.3 r2 17.3 r2-s1 17.3 r2-s2 17.3 r2-s3 17.3 r2-s4 17.3 r2-s5 17.3 r3 17.3 r3-s1 17.3 r3-s2 17.3 r3-s3 17.3 r3-s4 17.3 r3-s5 17.3 r3-s6 17.3 r3-s7 17.3 r3-s8 17.3 r3-s9 17.4 17.4 r1 17.4 r1-s1 17.4 r1-s2 17.4 r1-s3 17.4 r1-s4 17.4 r1-s5 17.4 r1-s6 17.4 r1-s7 17.4 r2 17.4 r2-s1 17.4 r2-s10 17.4 r2-s11 17.4 r2-s2 17.4 r2-s3 17.4 r2-s4 17.4 r2-s5 17.4 r2-s6 17.4 r2-s7 17.4 r2-s8 17.4 r2-s9 17.4 r3 17.4 r3-s1 17.4 r3-s2 17.4 r3-s3 18.1 18.1 r1 18.1 r2 18.1 r2-s1 18.1 r2-s2 18.1 r2-s4 18.1 r3 18.1 r3-s1 18.1 r3-s2 18.1 r3-s3 18.1 r3-s4 18.1 r3-s5 18.1 r3-s6 18.1 r3-s7 18.1 r3-s8 18.1 r3-s9 18.2 18.2 r1 18.2 r1-s2 18.2 r1-s3 18.2 r1-s4 18.2 r1-s5 18.2 r2 18.2 r2-s1 18.2 r2-s2 18.2 r2-s3 18.2 r2-s4 18.2 r2-s5 18.2 r2-s6 18.2 r2-s7 18.2 r3 18.2 r3-s1 18.2 r3-s2 18.3 18.3 r1 18.3 r1-s1 18.3 r1-s2 18.3 r1-s3 18.3 r1-s4 18.3 r1-s5 18.3 r1-s6 18.3 r2 18.3 r2-s1 18.3 r2-s2 18.3 r2-s3 18.3 r2-s4 18.3 r3 18.3 r3-s1 18.4 18.4 r1 18.4 r1-s1 18.4 r1-s2 18.4 r1-s3 18.4 r1-s4 18.4 r1-s5 18.4 r1-s6 18.4 r1-s7 18.4 r2 18.4 r2-s1 18.4 r2-s2 18.4 r2-s3 18.4 r3 19.1 19.1 r1 19.1 r1-s1 19.1 r1-s2 19.1 r1-s3 19.1 r1-s4 19.1 r1-s5 19.1 r2 19.1 r2-s1 19.1 r2-s2 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 19.2 r1-s5 19.2 r1-s6 19.3 19.3 r1 19.3 r1-s1 19.3 r2 19.3 r2-s1 19.3 r2-s2 19.3 r2-s3 19.3 r2-s4 19.3 r2-s5 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r1-s3

Affected range stops below 17.3R3-S10, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.4R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.1R3-S10, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.2R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.3R3-S2, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.4R2-S4, 18.4R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.1R3, 19.1R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.2R2, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.3R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.4R2, so it looks safe — our inference, not a vendor statement

juniper-qfx5100-96s (environment)

Qfx5100-96S · Juniperdevice

80%

All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://kb.juniper.net/JSA11129

References (1)

x_refsource_MISCVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11129

CVSS

5.8MEDIUMjuniper

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: CHANGED
Confidentiality: NONE
Integrity: NONE
Availability: LOW

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-665

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card