CVE-2024-30380

Service interruption via exceptional TLV handling

Published Apr 16, 2024 · Updated Aug 2, 2024

Improper exceptional-condition handling in Junos OS and Junos OS Evolved allows remote attackers to crash l2cpd with a specific TLV. The l2cpd process mishandles an exceptional condition while processing that TLV instead of rejecting it safely. The attacker must be adjacent to the device; repeated delivery sustains the interruption by repeatedly reinitializing STP-family, MVRP, and ERP protocols.

CVSS severity7.1
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper exceptional-condition handling in Junos OS and Junos OS Evolved allows remote attackers to crash l2cpd with a specific TLV. The l2cpd process mishandles an exceptional condition while processing that TLV instead of rejecting it safely. The attacker must be adjacent to the device; repeated delivery sustains the interruption by repeatedly reinitializing STP-family, MVRP, and ERP protocols.

The record

CVE
CVE-2024-30380
Published
Apr 16, 2024
Updated
Aug 2, 2024
Vendor
Juniper Networks
Product
Junos OS Evolved
Classifications
CWE-755, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 16, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <21.2R3-S7-EVO
  2. Affected versionversion=21.3 <21.3R3-S5-EVO
  3. Affected versionversion=21.4 <21.4R3-S5-EVO
  4. Affected versionversion=22.1 <22.1R3-S4-EVO
  5. Affected versionversion=22.2 <22.2R3-S2-EVO
  6. Affected versionversion=22.3 <22.3R2-S2-EVO, 22.3R3-S1-EVO
  7. Affected versionversion=22.4 <22.4R2-S2-EVO, 22.4R3-EVO
  8. Affected versionversion=23.2 <23.2R1-S1-EVO, 23.2R2-EVO

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Juniper Networks · Junos OS Evolvedversion=0 <21.2R3-S7-EVO; version=21.3 <21.3R3-S5-EVO; version=21.4 <21.4R3-S5-EVO; version=22.1 <22.1R3-S4-EVO; version=22.2 <22.2R3-S2-EVO; version=22.3 <22.3R2-S2-EVO, 22.3R3-S1-EVO; version=22.4 <22.4R2-S2-EVO, 22.4R3-EVO; version=23.2 <23.2R1-S1-EVO, 23.2R2-EVO
Juniper Networks · Junos OSversion=0 <20.4R3-S9; version=21.2 <21.2R3-S7; version=21.3 <21.3R3-S5; version=21.4 <21.4R3-S4; version=22.1 <22.1R3-S4; version=22.2 <22.2R3-S2; version=22.3 <22.3R2-S2, 22.3R3-S1; version=22.4 <22.4R2-S2, 22.4R3; version=23.2 <23.2R1-S1, 23.2R2

Published CVSS scores

6.5Juniper Networks, Inc.CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.1Juniper Networks, Inc.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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-755Improper Handling of Exceptional Conditions
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo