CVE Tools

CVE-2024-30402

Junos OS and Junos OS Evolved: The l2ald crashes on receiving telemetry messages from a specific subscription

No known exploitation. EPSS puts it in the 43rd percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Juniper Networks Junos OS EvolvedAffected: ≥ 21.4-EVO, < 21.4R3-S5-EVOUpgrade to: 21.4R3-S5-EVOAffected: ≥ 22.1-EVO, < 22.1R3-S4-EVOUpgrade to: 22.1R3-S4-EVOAffected: ≥ 22.2-EVO, < 22.2R3-S3-EVOUpgrade to: 22.2R3-S3-EVOAffected: ≥ 22.3-EVO, < 22.3R3-S1-EVOUpgrade to: 22.3R3-S1-EVO + 2 more branchesStated by: CVE record
  • Juniper Networks Junos OSAffected: ≥ 20.4, < 20.4R3-S10Upgrade to: 20.4R3-S10Affected: ≥ 21.2, < 21.2R3-S7Upgrade to: 21.2R3-S7Affected: ≥ 21.4, < 21.4R3-S5Upgrade to: 21.4R3-S5Affected: ≥ 22.1, < 22.1R3-S4Upgrade to: 22.1R3-S4 + 5 more branchesStated by: CVE record
  • Juniper JunosAffected: < 20.4Upgrade to: 20.4Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Layer 2 Address Learning Daemon (l2ald) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial of Service (DoS). When telemetry requests are sent to the device, and the Dynamic Rendering Daemon (drend) is suspended, the l2ald crashes and restarts due to factors outside the attackers control. Repeated occurrences of these events causes a sustained DoS condition. This issue affects: Junos OS: * All versions earlier than 20.4R3-S10; * 21.2 versions earlier than 21.2R3-S7; * 21.4 versions earlier than 21.4R3-S5; * 22.1 versions earlier than 22.1R3-S4; * 22.2 versions earlier than 22.2R3-S3; * 22.3 versions earlier than 22.3R3-S1; * 22.4 versions earlier than 22.4R3; * 23.2 versions earlier than 23.2R1-S2, 23.2R2. Junos OS Evolved: * All versions earlier than 21.4R3-S5-EVO; * 22.1-EVO versions earlier than 22.1R3-S4-EVO; * 22.2-EVO versions earlier than 22.2R3-S3-EVO; * 22.3-EVO versions earlier than 22.3R3-S1-EVO; * 22.4-EVO versions earlier than 22.4R3-EVO; * 23.2-EVO versions earlier than 23.2R2-EVO.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS43rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 804 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availableworkaround available, record updated
  3. Publishedweakness classified

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 5.9 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for JunOS, not every advisory.