# CVE-2024-30380: Junos OS and Junos OS Evolved: l2cpd crash upon receipt of a specific TLV

> An adjacent attacker can cause a sustained Denial of Service by crashing the l2cpd process via a specific TLV, disrupting Layer 2 protocols.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x7p5-c683-6jrp

## What is CVE-2024-30380?

CVE-2024-30380 is a high-severity denial of service vulnerability in Juniper Junos, published on 16 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2024-30380?

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

## How do I fix CVE-2024-30380?

No fix has been published for CVE-2024-30380 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30380 being exploited?

There is no known exploitation of CVE-2024-30380 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30380 and fix it if it is affected.

What it is: CVE-2024-30380 is a high-severity denial of service vulnerability in Juniper Junos, published on 16 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-30380 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30380/ (Markdown: https://insights.sbomify.com/CVE-2024-30380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30380
- OSV: https://osv.dev/vulnerability/CVE-2024-30380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30380/
Summaries are generated and may contain mistakes; the official description above is the record.