CVE-2024-30380

Junos OS and Junos OS Evolved: l2cpd crash upon receipt of a specific TLV

MEDIUM
6.5
CVSS Score
Published: April 16, 2024 at 08:04 PM UTC
Updated: June 17, 2026 at 07:26 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

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
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

An Improper Handling of Exceptional Conditions vulnerability in Juniper Networks Junos OS and Junos OS Evolved allows an adjacent unauthenticated attacker to cause a Denial of Service (DoS), which causes the l2cpd process to crash by sending a specific TLV. The l2cpd process is responsible for layer 2 control protocols, such as STP, RSTP, MSTP, VSTP, ERP, and LLDP.  The impact of the l2cpd crash is reinitialization of STP protocols (RSTP, MSTP or VSTP), and MVRP and ERP, leading to a Denial of Service.  Continued receipt and processing of this specific TLV will create a sustained Denial of Service (DoS) condition. This issue affects: Junos OS: all versions before 20.4R3-S9, from 21.2 before 21.2R3-S7, from 21.3 before 21.3R3-S5, from 21.4 before 21.4R3-S4, from 22.1 before 22.1R3-S4, from 22.2 before 22.2R3-S2, from 22.3 before 22.3R2-S2, 22.3R3-S1, from 22.4 before 22.4R2-S2, 22.4R3, from 23.2 before 23.2R1-S1, 23.2R2; Junos OS Evolved: all versions before 21.2R3-S7, from 21.3 before 21.3R3-S5-EVO, from 21.4 before 21.4R3-S5-EVO, from 22.1 before 22.1R3-S4-EVO, from 22.2 before 22.2R3-S2-EVO, from 22.3 before 22.3R2-S2-EVO, 22.3R3-S1-EVO, from 22.4 before 22.4R2-S2-EVO, 22.4R3-EVO, from 23.2 before 23.2R1-S1-EVO, 23.2R2-EVO.

Affected

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

Affected range stops below 20.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R2-S2, 22.3R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R2-S2, 22.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R1-S1, 23.2R2, so it looks safe — our inference, not a vendor statement
v < 21.2R3-S7-EVO21.3 ≤ v < 21.3R3-S5-EVO21.4 ≤ v < 21.4R3-S5-EVO22.1 ≤ v < 22.1R3-S4-EVO22.2 ≤ v < 22.2R3-S2-EVO22.3 ≤ v < 22.3R2-S2-EVO, 22.3R3-S1-EVO22.4 ≤ v < 22.4R2-S2-EVO, 22.4R3-EVO23.2 ≤ v < 23.2R1-S1-EVO, 23.2R2-EVO21.321.422.122.222.322.423.2
Affected range stops below 21.2R3-S7-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R2-S2-EVO, 22.3R3-S1-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R2-S2-EVO, 22.4R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R1-S1-EVO, 23.2R2-EVO, so it looks safe — our inference, not a vendor statement

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 exploitNot automatablePartial impact

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

CVSS

6.5MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-755

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