CVE-2023-28976

Junos OS: MX Series: If a specific traffic rate goes above the DDoS threshold it will lead to an FPC crash

HIGH
7.5
CVSS Score
Published: April 17, 2023 at 12:00 AM UTC
Updated: June 17, 2026 at 05:49 AM UTC
19 products affected across 2 vendorsJunosMx960Mx480

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
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). If specific traffic is received on MX Series and its rate exceeds the respective DDoS protection limit the ingress PFE will crash and restart. Continued receipt of this traffic will create a sustained DoS condition. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 19.1R3-S10; 19.2 versions prior to 19.2R3-S7; 19.3 versions prior to 19.3R3-S8; 19.4 versions prior to 19.4R3-S11; 20.2 versions prior to 20.2R3-S5; 20.4 versions prior to 20.4R3-S6; 21.1 versions prior to 21.1R3-S5; 21.2 versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R2.

Affected

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

v < 19.1v < 19.1R3-S1019.2 ≤ v < 19.2R3-S719.3 ≤ v < 19.3R3-S819.4 ≤ v < 19.4R3-S1120.2 ≤ v < 20.2R3-S520.4 ≤ v < 20.4R3-S621.1 ≤ v < 21.1R3-S521.2 ≤ v < 21.2R3-S421.3 ≤ v < 21.3R321.4 ≤ v < 21.4R322.1 ≤ v < 22.1R219.119.1 r119.1 r1-s119.1 r1-s219.1 r1-s319.1 r1-s419.1 r1-s519.1 r1-s619.1 r219.1 r2-s119.1 r2-s219.1 r2-s319.1 r319.1 r3-s119.1 r3-s219.1 r3-s319.1 r3-s419.1 r3-s519.1 r3-s619.1 r3-s719.1 r3-s819.1 r3-s919.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.2 r1-s419.2 r1-s519.2 r1-s619.2 r1-s719.2 r1-s819.2 r1-s919.2 r219.2 r2-s119.2 r319.2 r3-s119.2 r3-s219.2 r3-s319.2 r3-s419.2 r3-s519.2 r3-s619.319.3 r119.3 r1-s119.3 r219.3 r2-s119.3 r2-s219.3 r2-s319.3 r2-s419.3 r2-s519.3 r2-s619.3 r2-s719.3 r319.3 r3-s119.3 r3-s219.3 r3-s319.3 r3-s419.3 r3-s519.3 r3-s619.3 r3-s719.419.4 r119.4 r1-s119.4 r1-s219.4 r1-s319.4 r1-s419.4 r219.4 r2-s119.4 r2-s219.4 r2-s319.4 r2-s419.4 r2-s519.4 r2-s619.4 r2-s719.4 r319.4 r3-s119.4 r3-s1019.4 r3-s219.4 r3-s319.4 r3-s419.4 r3-s519.4 r3-s619.4 r3-s719.4 r3-s819.4 r3-s920.220.2 r120.2 r1-s120.2 r1-s220.2 r1-s320.2 r220.2 r2-s120.2 r2-s220.2 r2-s320.2 r320.2 r3-s120.2 r3-s220.2 r3-s320.2 r3-s420.420.4 r120.4 r1-s120.4 r220.4 r2-s120.4 r2-s220.4 r320.4 r3-s120.4 r3-s220.4 r3-s320.4 r3-s420.4 r3-s521.121.1 r121.1 r1-s121.1 r221.1 r2-s121.1 r2-s221.1 r321.1 r3-s121.1 r3-s221.1 r3-s321.1 r3-s421.221.2 r121.2 r1-s121.2 r1-s221.2 r221.2 r2-s121.2 r2-s221.2 r321.2 r3-s121.2 r3-s221.2 r3-s321.321.3 r121.3 r1-s121.3 r1-s221.3 r221.3 r2-s121.3 r2-s221.421.4 r121.4 r1-s121.4 r1-s221.4 r221.4 r2-s121.4 r2-s222.122.1 r122.1 r1-s122.1 r1-s2
Affected range stops below 19.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S10, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R3-S11, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R2, so it looks safe — our inference, not a vendor statement
juniper-mx (environment) · juniper-mx10 (environment) · juniper-mx10000 (environment) · juniper-mx10003 (environment) · juniper-mx10008 (environment) · juniper-mx10016 (environment) · juniper-mx104 (environment) · juniper-mx150 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx204 (environment) · juniper-mx240 (environment) · juniper-mx40 (environment) · juniper-mx480 (environment) · juniper-mx5 (environment) · juniper-mx80 (environment) · juniper-mx960 (environment)
80%
All versions
All versions
All versions
All versions
All versions
All versions
All versions
All versions
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

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-754

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.

Free plan, no card